Created attachment 390224 [details] cross-x86_64-w64-mingw64-gcc-stage1.log After running crossdev --target x86_64-w64-mingw64 it fails at step: Emerging cross-gcc-stage1 ... The error in the log file is: options.c:1046:3: error: ‘HAVE_GAS_ALIGNED_COMM’ was not declared in this scope HAVE_GAS_ALIGNED_COMM, /* use_pe_aligned_common */ ^
I have the same issue with x86_64-w64-mingw64. I also tried to run crossdev -t i686-w64-mingw64 But this files because: *** BFD does not support target i686-w64-mingw64. *** Look in bfd/config.bfd for supported targets. In bfd/config.bdf I found these lines: x86_64-*-mingw* | x86_64-*-pe | x86_64-*-pep | x86_64-*-cygwin) i[3-7]86-*-mingw32* | i[3-7]86-*-cygwin* | i[3-7]86-*-winnt | i[3-7]86-*-pe) As I understood from reading... crossdev -t help | grep mingw - mingw32 http://www.mingw.org/ - mingw64 http://mingw-w64.sourceforge.net/ i686-w64-mingw64 should give me a MinGW-w64 (the fork of MinGW) based toolchain for 32bit targets. x86_64-w64-mingw64 should give me a MinGW-w64 based toolchain for 64bit targets. Whereas i686-w64-mingw32 x86_64-w64-mingw32 should give me the equivalents based on the original MinGW. Did I get this right? Or is the help text wrong? Or do I miss something else?
(In reply to Lars from comment #1) the section in the help you've quoted is for special pseudo targets. that is, you run them verbatim: crossdev mingw64 and crossdev will rewrite that to the full tuple. in this case, pretty sure you want to use x86_64-w64-mingw32.
