> > No fix yet :-( Haven't had the time to dig into it properly, but I
> > think we can now safely say it's not a local issue in
> Joachims build
> > env :-)
> >
> > If you just run a dumpbin command (the same way) manually with a
> > ">foo", does it redirect it properly then? Or is dumpbin for some
> > reason not writing on stdout?
> >
> > It runs perfectly on two completely separate build envs I have here
> > :-O
>
> Here's another interesting tidbit for you: if I run the
> gendef.pl script by hand from the visual studio command
> prompt thing (the one I can't compile from), it works fine.

Funky.
Can you try having it run the dumpbin command into a tempfile, and then
open-and-read that tempfile, to see if that makes a difference?
(Assuming you know enough perl to do that, of course)

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

On Tue, Oct 03, 2006 at 12:27:47AM -0700, Jeremy Drake wrote:
> On Tue, 3 Oct 2006, Magnus Hagander wrote:

> > Funky.
> > Can you try having it run the dumpbin command into a tempfile, and then
> > open-and-read that tempfile, to see if that makes a difference?
> > (Assuming you know enough perl to do that, of course)

> Doing it as
> system("dumpbin /symbols $_ > $tmpfn")
> still output to the console.

I could redirect it with "... 2>&1 > file" IIRC, the /out:FILE seems to be
the cleaner approach however :-)


Joachim


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings