On Wed, Apr 21, 2010 at 6:05 AM, Sisyphus <sisyph...@optusnet.com.au> wrote: > > ----- Original Message ----- From: "Doug Semler" <dougsem...@gmail.com> > To: "Sisyphus" <sisyph...@optusnet.com.au> > Cc: "mingw64" <mingw-w64-public@lists.sourceforge.net> > Sent: Wednesday, April 21, 2010 2:45 AM > Subject: Re: [Mingw-w64-public] [Repost] LIBRARY_PATH environment variable > not honoured. > > >> Oops, should have qualified that - i meant the output during >> compile....IOW make CFLAGS=-v > > If I run 'x86_64-w64-mingw32-gcc -c try.c -v' (where try.c is a simple > "hello" script), will that give you all you need ? (Ouptut attached.) It > occurred to me later at work (where I had no internet connection) that you > were probably after that. > > If that's still not right, just yell at me and I'll do as you asked above > :-) > > I see a LIBRARY_PATH specified in the output - that has nothing to do with > my LIBRARY_PATH env var. (If I remove that environment variable, I still get > the same result.) >
Well, it looks like the compiler may be being built with host != target... In other words it wasn't bootstrapped and has been configured as a cross compiler... LIBRARY_PATH is ignored in cross compilers. The buildbot that builds this should probably override the configuration guess, by both passing the --host=x86_64-w64-mingw32 on the configure line, and also by passing --enable-bootstrap if it's being built on a 64 windows machine. I don't know how well this would work, but it could be tried.... If host != target, CROSS_DIRECTORY_STRUCTURE is defined, which then turns off several environment variables (that wouldn't be suitable for a cross compiler)... ------------------------------------------------------------------------------ _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
