On Mon, Sep 6, 2010 at 11:15 PM, John E. / TDM <[email protected]> wrote:
> It is correct that TDM64 GCC does not include a "lib64" directory of any > sort (symlink or copy). I've simply never found it necessary when building > GCC or any of the other software I build on a regular basis. > > Since GCC searches the "lib" directory just fine, I guess I fail to see > where the problem is. I would only expect to see a lib64 directory when > working with a multilib i686-w64-mingw32 compiler, which TDM64 GCC is not > (it's multilib x86_64-w64-mingw32). > Sorry I am not a compiler expert here. What is the difference between a multilib x86_64-w64-mingw32 compiler and a multilib i686-w64-mingw32 compiler? And from Kai Tietz. "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)." This seems to be the safer options as far as I know. Even for non-multilib tool chains, it seems to be necessary. -- Xiaofan ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
