On 9/7/2010 10:07, Xiaofan Chen wrote: > On Tue, Sep 7, 2010 at 9:40 AM, JonY<[email protected]> wrote: >> 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). >> > > Yes that is what I did and that fixed all the issues. >
Ok, to clear everything up, for non-multilib 4.6, you should only have "lib", "lib64" only if you have non-multilib 4.5. This sounds like an installation problem. Glad that you got it fixed. This is why I suggested linking lib64 and lib for 64bit target toolchains to make them identical, it works for both 4.5.x and 4.6.x. Its not compulsory or required at all, but you could say it works around such issues. ------------------------------------------------------------------------------ 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
