[Python-checkins] cpython: test that the compiler support -Werror=statement-after-declaration before using
benjamin.peterson
python-checkins at python.org
Mon May 20 17:23:57 CEST 2013
http://hg.python.org/cpython/rev/e47806951fb2
changeset: 83863:e47806951fb2
parent: 83861:6d2f0edb0758
user: Benjamin Peterson <benjamin at python.org>
date: Mon May 20 08:22:04 2013 -0700
summary:
test that the compiler support -Werror=statement-after-declaration before using it
files:
configure | 45 ++++++++++++++++++++++++++++++++++++++-
configure.ac | 24 +++++++++++++++++++-
2 files changed, 65 insertions(+), 4 deletions(-)
diff --git a/configure b/configure
--- a/configure
+++ b/configure
@@ -6264,8 +6264,6 @@
# tweak BASECFLAGS based on compiler and platform
case $GCC in
yes)
- BASECFLAGS="$BASECFLAGS -Werror=declaration-after-statement"
-
# Python doesn't violate C99 aliasing rules, but older versions of
# GCC produce warnings for legal Python code. Enable
# -fno-strict-aliasing on versions of GCC that support but produce
@@ -6379,6 +6377,49 @@
BASECFLAGS="$BASECFLAGS -Wno-unused-result"
fi
+ { $as_echo "$as_me:${as_lineno-$LINENO}: checking for -Werror=declaration-after-statement" >&5
+$as_echo_n "checking for -Werror=declaration-after-statement... " >&6; }
+ ac_save_cc="$CC"
+ CC="$CC -Werror=declaration-after-statement"
+ save_CFLAGS="$CFLAGS"
+ if ${ac_cv_declaration_after_statement_warning+:} false; then :
+ $as_echo_n "(cached) " >&6
+else
+ cat confdefs.h - <<_ACEOF >conftest.$ac_ext
+/* end confdefs.h. */
+
+
+int
+main ()
+{
+
+ ;
+ return 0;
+}
+
+_ACEOF
+if ac_fn_c_try_compile "$LINENO"; then :
+
+ ac_cv_declaration_after_statement_warning=yes
+
+else
+
+ ac_cv_declaration_after_statement_warning=no
+
+fi
+rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
+fi
+
+ CFLAGS="$save_CFLAGS"
+ CC="$ac_save_cc"
+ { $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_declaration_after_statement_warning" >&5
+$as_echo "$ac_cv_declaration_after_statement_warning" >&6; }
+
+ if test $ac_cv_declaration_after_statement_warning = yes
+ then
+ BASECFLAGS="$BASECFLAGS -Werror=declaration-after-statement"
+ fi
+
# if using gcc on alpha, use -mieee to get (near) full IEEE 754
# support. Without this, treatment of subnormals doesn't follow
# the standard.
diff --git a/configure.ac b/configure.ac
--- a/configure.ac
+++ b/configure.ac
@@ -1127,8 +1127,6 @@
# tweak BASECFLAGS based on compiler and platform
case $GCC in
yes)
- BASECFLAGS="$BASECFLAGS -Werror=declaration-after-statement"
-
# Python doesn't violate C99 aliasing rules, but older versions of
# GCC produce warnings for legal Python code. Enable
# -fno-strict-aliasing on versions of GCC that support but produce
@@ -1186,6 +1184,28 @@
BASECFLAGS="$BASECFLAGS -Wno-unused-result"
fi
+ AC_MSG_CHECKING(for -Werror=declaration-after-statement)
+ ac_save_cc="$CC"
+ CC="$CC -Werror=declaration-after-statement"
+ save_CFLAGS="$CFLAGS"
+ AC_CACHE_VAL(ac_cv_declaration_after_statement_warning,
+ AC_COMPILE_IFELSE(
+ [
+ AC_LANG_PROGRAM([[]], [[]])
+ ],[
+ ac_cv_declaration_after_statement_warning=yes
+ ],[
+ ac_cv_declaration_after_statement_warning=no
+ ]))
+ CFLAGS="$save_CFLAGS"
+ CC="$ac_save_cc"
+ AC_MSG_RESULT($ac_cv_declaration_after_statement_warning)
+
+ if test $ac_cv_declaration_after_statement_warning = yes
+ then
+ BASECFLAGS="$BASECFLAGS -Werror=declaration-after-statement"
+ fi
+
# if using gcc on alpha, use -mieee to get (near) full IEEE 754
# support. Without this, treatment of subnormals doesn't follow
# the standard.
--
Repository URL: http://hg.python.org/cpython
More information about the Python-checkins
mailing list