Follow-up Comment #9, bug #40227 (project make): > (Btw, what is gnumake32.exe in your case, and how is it different from gnumake64.exe?)
Sorry if that wasn't clear: gnumake32.exe was built with the 32-bits toolchain from MinGW-w64, and gnumake64.exe was built with the 64-bits toolchain from MinGW-w64. Only the 64-bits build presents this issue, which is also why you don't see it with the (32-bits, obviously) build done with the mingw.org toolchain. > So we need some other preprocessor symbols. Right. What about simply _WIN64, as it doesn't seem that mingw.org will support that anytime soon? Moreover I just found out that in MinGW-w64 the support for _vsnprintf_s function dates back nearly from the beginning of the project, so no need for a version check. Besides, I tried -D__USE_MINGW_ANSI_STDIO=1 and this was also enough to fix the issue, indeed! So this is probably the way to go. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?40227> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/ _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make