lmi-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lmi-commits] [5966] Don't use -std=c++0x switch when building using con


From: Vadim Zeitlin
Subject: [lmi-commits] [5966] Don't use -std=c++0x switch when building using configure.
Date: Mon, 06 Oct 2014 17:37:25 +0000

Revision: 5966
          http://svn.sv.gnu.org/viewvc/?view=rev&root=lmi&revision=5966
Author:   zeitlin
Date:     2014-10-06 17:37:25 +0000 (Mon, 06 Oct 2014)
Log Message:
-----------
Don't use -std=c++0x switch when building using configure.

Use -Wno-variadic-macros instead, which works with g++ 4 and avoids
introducing gratuitous difference between the builds using configure and
makefiles and possible binary incompatibilities (as code compiled in C++98 and
C++11 mode is not binary compatible under Unix).

Modified Paths:
--------------
    lmi/trunk/configure.ac

Modified: lmi/trunk/configure.ac
===================================================================
--- lmi/trunk/configure.ac      2014-10-06 17:37:19 UTC (rev 5965)
+++ lmi/trunk/configure.ac      2014-10-06 17:37:25 UTC (rev 5966)
@@ -556,6 +556,7 @@
     -Wimport \
     -Wmultichar \
     -Wno-long-long \
+    -Wno-variadic-macros \
     -Wpacked \
     -Wpointer-arith \
     -Wsign-compare \
@@ -575,15 +576,6 @@
         -Wpmf-conversions \
         -Wsynth"
 
-    dnl g++ 4.4 doesn't compile wxWidgets code that relies on use of empty
-    dnl macro arguments, because it's behavior undefined by the standard
-    dnl prior to C++0x or C99; if the compiler is too old to understand
-    dnl -std=c++0x, it's also too old to complain about this and so we can
-    dnl use -std=c++98
-    AX_CXX_CHECK_FLAG([-std=c++0x],[],[],
-                      [CXXFLAGS="$CXXFLAGS -std=c++0x"],
-                      [CXXFLAGS="$CXXFLAGS -std=c++98"])
-
     dnl we need to use this option with g++ 4.3 to prevent its complaints
     dnl about "-funit-at-a-time is required for inlining of functions that are
     dnl only called once" in debug builds




reply via email to

[Prev in Thread] Current Thread [Next in Thread]