On 4/26/2011 02:11, Jon wrote: > I've started evaluating mingw-w32-1.0-bin_i686-mingw_20110422.zip as a > toolchain where I typically use the 32-bit 4.5.2 version from > http://tdm-gcc.tdragon.net/ > > The build environment uses LIBRARY_PATH and works fine with tdm-gcc 4.5.2 but > fails with the mingw-w64 toolchain because ld can't find some of the > libraries. > > I'm not done with testing, but it appears that the LIBRARY_PATH issue is the > root cause of my build failures. For the mingw-w64 case I inject the name > prefixed binaries from bin/ into the environment rather than use configure's > --host; config.log indicates that mingw-w64 isn't cross-compiling. >
I think cross compilers ignore LIBRARY_PATH, but I'm not very sure of this. I think you can try using --host= --build= set to the same value instead of beating around the bush with environment variables. > I've read the https://sourceforge.net/mailarchive/message.php?msg_id=25062006 > thread and would like to know the latest mingw-w64 recommendations for using > LIBRARY_PATH. While I would like to be able to use LIBRARY_PATH as I do with > other MinGW-based toolchains, is there another env var or setting other than > -L I should be using? > Looks like it does ignore it, so avoid using LIBRARY_PATH. For autotool'ed buildsystems, use LDFLAGS=-L.../lib and CPPFLAGS=-I.../include to point to additional search locations.
0xED74C077.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
