Follow-up Comment #6, bug #40227 (project make):
I found the _vsnprintf_s declaration in my MinGW installation:
.../mingw64/x86_64-w64-mingw32/include/sec_api/stdio_s.h
And this gets included from <stdio.h>.
I suppose this must be a relatively recent addition,
as I installed that version today (major.minor is 3.11).
I added a version check to the patch, the numbers can be
refined to pinpoint the introduction of _vsnprintf_s, if
the approach is found to be valid and no better fix is
found.
Back to the issue itself. Here are a few quick ways to
reproduce it reliably.
First without a Makefile:
$ ./gnumake64 -f no-Makefile
gnumake64:
gnumake64: ***. Stop.
$ ./gnumake32 -f no-Makefile
gnumake32: no-Makefile: No such file or directory
gnumake32: *** No rule to make target 'no-Makefile'. Stop.
or with a minimal Makefile, which I inline here using --eval,
but the effect is the same with a Makefile containing that
single line:
$ ./gnumake64.exe --eval "FORCE:;" FORCE
gnumake64:
$ ./gnumake32.exe --eval "FORCE:;" FORCE
gnumake32: 'FORCE' is up to date.
Updated patch: 0004b-MinGW-also-needs-the-msc_vsnprintf-replacement-for-.patch
(file #29376)
_______________________________________________________
Additional Item Attachment:
File name: 0004b-MinGW-also-needs-the-msc_vsnprintf-replacement-for-.patch
Size:1 KB
_______________________________________________________
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
