Hi, Richard Frith-Macdonald wrote:
It's a mistake/bug, or maybe they think people using mingw64 actually want to cross-compile for mingw32 (seems perverse). Anyway, it can be overridden by using --host=mingw64 when configuring gnustep-make, as a command line argument takes precedence over information from config.site
I actually found this informative info, which in case would also allow us to distinguis between the original mingw and mingw, if needed, the key is the w64 vs. pc
Citing: This triplet specifies where the executables produced by this program (gcc) will run. Originally the MinGW.org project chose `*-pc-mingw32`, so we selected `*-w64-mingw32` to avoid the conflict. There is no special meaning about `w64` itself. `mingw32` on the other hand specifies the ABI, so all `i686-*-mingw32` targets are considered ABI-compatible. Neither does `w64` specify the target is 64-bit, nor does `mingw32` specify the target is 32-bit. They are just hard-coded names.
