[evolution-data-server] Bug 626090 - Only set -fno-strict-aliasing for GCC

[Matthew Barnes <mbarnes src gnome org>]

commit 5eed53f0aaaa8c971983c5f955f5531f1c0d33fe
Author: Matthew Barnes <mbarnes redhat com>
Date:   Thu Aug 5 08:42:57 2010 -0400

    Bug 626090 - Only set -fno-strict-aliasing for GCC

 configure.ac |   17 +++++++++++------
 1 files changed, 11 insertions(+), 6 deletions(-)
---
diff --git a/configure.ac b/configure.ac
index 9c650df..4560f77 100644
--- a/configure.ac
+++ b/configure.ac
@@ -197,12 +197,6 @@ dnl	-Wmissing-format-attribute
 dnl	-Wshadow
 dnl	-Wstrict-aliasing=2
 
-dnl GCC 4.4 got more aggressive in its aliasing optimizations, changing
-dnl behavior that -- according to the C99 standard -- is supposed to be
-dnl undefined.  We may still have aliasing abuses lying around that rely
-dnl on GCC's previous "undefined" behavior, so disable strict-aliasing
-dnl optimization until we can find and fix all the abuses.
-dnl XXX This really belongs in AM_CFLAGS.
 AM_CPPFLAGS="$WARNING_FLAGS -fno-strict-aliasing"
 AC_SUBST(AM_CPPFLAGS)
 
@@ -228,6 +222,17 @@ case $YACC in
 	;;
 esac
 
+dnl GCC 4.4 got more aggressive in its aliasing optimizations, changing
+dnl behavior that -- according to the C99 standard -- is supposed to be
+dnl undefined.  We may still have aliasing abuses lying around that rely
+dnl on GCC's previous "undefined" behavior, so disable strict-aliasing
+dnl optimization until we can find and fix all the abuses.
+dnl (AC_PROG_CC must run first to set the GCC variable.)
+dnl XXX This really belongs in AM_CFLAGS.
+if test "x${GCC}" = "xyes"; then
+	CFLAGS="$CFLAGS -fno-strict-aliasing"
+fi
+
 dnl ******************************
 dnl Test whether jw is installed
 dnl ******************************