diff options
| author | Andres Freund | 2018-08-16 08:32:05 +0000 |
|---|---|---|
| committer | Andres Freund | 2018-08-16 08:32:05 +0000 |
| commit | 86d78ef50e0195f8181f2b0bd9540f4ddfb73480 (patch) | |
| tree | 5ebb642529159847eefb533cad7dd9ec5b3c169d /configure.in | |
| parent | 3593579bcdc77a70e0f987dca6d47f0bf1337f76 (diff) | |
Try to enable C99 in configure, but do not rely on it (yet).
Based on recent discussion it seems possible that we might start to
rely on more of C99. A prerequisite for that is enabling support for
that on used compilers.
Let's see on which buildfarm members autoconf's AC_PROG_CC_C99() is
sufficient to do so. There's probably at least one member where the
compiler is too old, but that'd probably be OK.
If we go for this permanently we'd likely want to clean out / up a few
other configure tests.
Note this does not touch the msvc build infrastructure, which'd need
separate treatment.
Discussion: https://postgr.es/m/20180815222401.kxsupl5zie2jgi4x@alap3.anarazel.de
Diffstat (limited to 'configure.in')
| -rw-r--r-- | configure.in | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/configure.in b/configure.in index 49257e53010..24372b6cee8 100644 --- a/configure.in +++ b/configure.in @@ -358,6 +358,7 @@ case $template in esac AC_PROG_CC([$pgac_cc_list]) +AC_PROG_CC_C99() AC_PROG_CXX([$pgac_cxx_list]) # Check if it's Intel's compiler, which (usually) pretends to be gcc, |