mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-12-27 08:39:28 +08:00
751f532b97
The method we've traditionally used, of redeclaring strerror_r() to see if the compiler complains of inconsistent declarations, turns out not to work reliably because some compilers only report a warning, not an error. Amazingly, this has gone undetected for years, even though it certainly breaks our detection of whether strerror_r succeeded. Let's instead test whether the compiler will take the result of strerror_r() as a switch() argument. It's possible this won't work universally either, but it's the best idea I could come up with on the spur of the moment. We should probably back-patch this once the dust settles, but first let's see what the buildfarm thinks of it. Discussion: https://postgr.es/m/10877.1537993279@sss.pgh.pa.us |
||
---|---|---|
.. | ||
ac_func_accept_argtypes.m4 | ||
ax_prog_perl_modules.m4 | ||
ax_pthread.m4 | ||
c-compiler.m4 | ||
c-library.m4 | ||
config.guess | ||
config.sub | ||
docbook.m4 | ||
general.m4 | ||
install-sh | ||
libtool.m4 | ||
llvm.m4 | ||
Makefile | ||
missing | ||
perl.m4 | ||
pkg.m4 | ||
prep_buildtree | ||
programs.m4 | ||
python.m4 | ||
tcl.m4 |