> Yes exactly. The x86_64-...-win32 toolchain is built as a cross-compiler. > > If you want no prefix, use the x86_64-...-win64 toolchain (if you have a > 64-bit OS, which you really should in this day and age ;-)).
This is rather the opposite problem! I already have a win 64bit native toolchain which works, but here I wanted a compiler building on a win64 machine (because I have a 64-bit OS!) for 32-bit hosts (because several end users still have 32-bit machines). This is why I downloaded the i686-w64-mingw32-gcc-4.8.0-win64 But as my 64-bit OS still can execute 32-bit code :) , I'll go for the win32 native... > > any case, the autotools configure invocation is the same regardless > prefixes: > > --host=x86_64-w64-mingw32 > > as explained on the wiki: > http://sourceforge.net/apps/trac/mingw-w64/wiki/MSYS > > The same applies for cross-compiling from Linux. Note that some crappy > autotools scripts (like that of GMP) need special magic to work in a > general cross-compiler scenario (see > https://github.com/rubenvb/MinGW-w64-build-scripts/blob/master/scripts/gmp.sh) > which needs explicit CC,CXX, etc... set at configure time. That's the issue. I depend on several libs with crappy scripts, which are not very mingw friendly (they detect mingw, and do stupid things, while they work better when I comment the mingw detection... probably crap from old mingw's), and very cross-compiler unfriendly. Thanks for helping! ------------------------------------------------------------------------------ Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
