Tom Lane 46b5e7c4b5 Revert "Distinguish printf-like functions that support %m from those that don't." ... This reverts commit 3a60c8ff89. Buildfarm results show that that caused a whole bunch of new warnings on platforms where gcc believes the local printf to be non-POSIX-compliant. This problem outweighs the hypothetical-anyway possibility of getting warnings for misuse of %m. We could use gnu_printf archetype when we've substituted src/port/snprintf.c, but that brings us right back to the problem of not getting warnings for %m. A possible answer is to attack it in the other direction by insisting that %m support be included in printf's feature set, but that will take more investigation. In the meantime, revert the previous change, and update the comment for PGAC_C_PRINTF_ARCHETYPE to more fully explain what's going on. Discussion: https://postgr.es/m/2975.1526862605@sss.pgh.pa.us		2018-08-12 18:46:01 -04:00
..
ac_func_accept_argtypes.m4
ax_prog_perl_modules.m4
ax_pthread.m4
c-compiler.m4	Revert "Distinguish printf-like functions that support %m from those that don't."	2018-08-12 18:46:01 -04:00
c-library.m4	Remove configure's check for nonstandard "long long" printf modifiers.	2018-05-23 14:19:04 -04:00
config.guess	Update config.guess and config.sub	2018-06-11 08:54:58 -04:00
config.sub	Update config.guess and config.sub	2018-06-11 08:54:58 -04:00
docbook.m4
general.m4
install-sh
libtool.m4
llvm.m4	LLVMJIT: Adapt to API changes in gdb and perf support.	2018-07-22 21:13:34 -07:00
Makefile
missing
perl.m4
pkg.m4
prep_buildtree
programs.m4
python.m4
tcl.m4