[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    branches/KDE/3.5/kde-common/admin
From:       Adriaan de Groot <groot () kde ! org>
Date:       2006-01-31 23:55:55
Message-ID: 1138751755.566054.16358.nullmailer () svn ! kde ! org
[Download RAW message or body]

SVN commit 504414 by adridg:

Revert last (o noes, ping-pong with coolo) because it breaks configure on all (?) \
non-gcc-2.95 platforms, though I can't see why it would.  Is there a reason to put \
the space in the variable instead of introducing a possibly superfluous space in \
CXXFLAGS? It looks scary like this. GCC 3.4 users can now compile as before.

 M  +2 -3      acinclude.m4.in  


--- branches/KDE/3.5/kde-common/admin/acinclude.m4.in #504413:504414
@@ -3095,12 +3095,11 @@
   AC_PROG_CPP
 
   if test "$GCC" = "yes"; then
-    KDE_CHECK_COMPILER_FLAG(fno-reorder-blocks,[gcc_noreorderblocks=" \
-fno-reorder-blocks"])  if test "$kde_use_debug_code" != "no"; then
       if test $kde_use_debug_code = "full"; then
         CFLAGS="-g3 -fno-inline $CFLAGS"
       else
-        CFLAGS="-g -O2$gcc_noreorderblocks -fno-schedule-insns -fno-inline $CFLAGS"
+        CFLAGS="-g -O2 -fno-reorder-blocks -fno-schedule-insns -fno-inline $CFLAGS"
       fi
     else
       CFLAGS="-O2 $CFLAGS"
@@ -3135,7 +3134,7 @@
         if test "$kde_use_debug_code" = "full"; then
           CXXFLAGS="-g3 -fno-inline $CXXFLAGS"
         else
-          CXXFLAGS="-g -O2$gcc_noreorderblocks -fno-schedule-insns -fno-inline \
$CXXFLAGS" +          CXXFLAGS="-g -O2 -fno-reorder-blocks -fno-schedule-insns \
-fno-inline $CXXFLAGS"  fi
       fi
       KDE_CHECK_COMPILER_FLAG(fno-builtin,[CXXFLAGS="-fno-builtin $CXXFLAGS"])


[prev in list] [next in list] [prev in thread] [next in thread]