On 9/6/2010 21:13, Kai Tietz wrote: > 2010/9/6 Xiaofan Chen<xiaof...@gmail.com>: >> On Mon, Sep 6, 2010 at 7:26 PM, JonY<jo...@users.sourceforge.net> wrote: >>> Are you using a multilib setup? There should not be a lib64 directory around >>> for non-multilib toolchains. >>> >>> If you are using a multilib setup, lib is where the arch default libraries >>> are. For x86_64-w64-mingw32, lib points to lib64. >>> >> >> BTW, for TDM64 (4.5.1), which is supposed to be multilib setup, >> there is not lib64 directory. In the end I have to copy the lib64 >> directory to lib in order to build libusb-1.0 Windows backend. >> >> >> -- >> Xiaofan > > Just to make here some notes about library directories and their > changed behavior. In older gcc toolchains (4.5.x and before) the > target libraries for multilib were lib32 for 32-bit, lib64 for 64-bit, > and lib is the folder to default's target. Either lib32 or lib64 > should be symbolic links to lib (dependent to the default target > used). > > For gcc 4.6 this behavior changes (along with a lot of other stuff, > too). We use now just lib& lib32 for 64-bit defaulted toolchains (no > lib64 is searched anymore). For 32-bit defaulted toolchains just lib& > lib64 are searched. > > Also for 4.6 (for having a working float.h, stddef.h, etc) it is > recommented not to use the environment of an earilers toolchain (4.5.x > or before) for build. This is caused by changes to gcc's internal > header search order. For 4.6 the internal gcc headers get always > searched first and those are forwarding by include_next to our > toolchain headers. > Please use in general the same version for doing native builds of the > compiler. > > Best regards, > Kai
I think I can see where the problem is, but I'm still guessing at this point. TDM multilib has lib and lib32, but your non-multilib has lib and lib64, and they are not linked. I suppose the fix is to move all the contents in lib (or lib64) to lib64 (or lib depending on your gcc version). ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
