2012/3/12 Ian Lance Taylor <iant@xxxxxxxxxx>: > > To be honest I don't see that in the pastebin. The use of -m64 should > cause the multilib support to kick in, and in particular should cause > the gcc driver to add /../lib64 to the end of the -L paths. I guess > that is not happening, but I can't see it from the log. In the fourth line uccurs linking 64bit libgcc_s_sjlj-1.dll. In this you can see by searching for 'm64'. Also, in the fourth line you can see the path used to search for 64bit CRT, and make sure that the path is used only for 32bit CRT. > > It might be helpful to show us the output of each of these commands: > > gcc --print-multi-lib $ i686-w64-mingw32-gcc --print-multi-lib .; 64;@m64 > gcc --print-multi-directory $ i686-w64-mingw32-gcc --print-multi-directory . > gcc --print-multi-directory -m32 $ i686-w64-mingw32-gcc --print-multi-directory -m32 . > gcc --print-multi-directory -m64 $ i686-w64-mingw32-gcc --print-multi-directory -m64 64 > > Ian -- Regards, niXman
