Windows 10 uses unimplemented 64-bit compiler [u920]

Reporter: Solitudinal  |  Status: open  |  Last Modified: October 05, 2017, 05:21:26 PM

Running Windows 10 at revision 34e3c17 and try to build a simple game produces quite a few fatal complaints about the -m64 flag and the error "sorry, unimplemented: 64-bit mode not compiled in"

Upon further investigation, this flag appears thanks to Compilers/Windows/gcc64.ey
even though, allegedly (or at least according to greg__), the compiler included is not 64-bit.

At any rate, one workaround is to always keep going into the Configuration Manager/Game Settings > ENIGMA > API > Compiler and change it from MinGW GCC G++ 64bit to just MinGW GCC G++
Alternatively, I've been told I can just delete gcc64.ey
Personally, I've taken the wimpy route of resetting to a prior stable revision due to other unrelated errors being present.

Harri committed that compiler descriptor nearly two years ago, and no one has modified the compiler selection algorithm since... what revision are you able to run at without deleting gcc64.ey?

Same here this one is getting on my nerves too, I don't want to have to keep switching. I thought it was because I had mingw64 installed, now I don't know if it is.

This bug is because gcc64.ey and gcc.ey are both flagged as native in the ey file. We will be doing away with the portable zip soon in favor of a msys2 install. msys2 handles setting the %path% for 32bit and 64bit toolchains depending on the exe you launch therefore, we will only need one ey for gcc on windows.
Please sign in to post comments, or you can view this issue on GitHub.