# HG changeset patch
# User al
# Date 1351340546 0
# Node ID b534bdb14c5f0ce33ea409e4d8a3b7681c73523f
# Parent  1a50a0bcd444a3ce90cfacd221ed6aaf91ea7dee
build/configure: Move addition of extra CFLAGS further down

The test is know made on cc_vendor after we correctly identified
the compiler. Before we were just assuming if the program is named
cc it is GCC.

For the record:
The condition may still/or in future be wrong for some compilers on
darwin and I doubt the flags are really necessary nowadays.

Patch by Xidorn Quan >quanxunzhen gmail.com<

diff -r 1a50a0bcd444 -r b534bdb14c5f configure
--- a/configure	Fri Oct 26 19:06:50 2012 +0000
+++ b/configure	Sat Oct 27 12:22:26 2012 +0000
@@ -1577,9 +1577,6 @@
 
 if darwin; then
   extra_cflags="-mdynamic-no-pic $extra_cflags"
-  if test "$(basename $_cc)" != "clang" ; then
-    extra_cflags="-falign-loops=16 -shared-libgcc $extra_cflags"
-  fi
   _timer=timer-darwin.c
 fi
 
@@ -1725,6 +1722,10 @@
 fi # icc
 test "$cc_fail" = yes && die "unsupported compiler version"
 
+if darwin && test "$cc_vendor" != "clang" ; then
+  extra_cflags="-falign-loops=16 -shared-libgcc $extra_cflags"
+fi
+
 echocheck "working compiler"
 cflag_check "" || die "Compiler is not functioning correctly. Check your installation and custom CFLAGS $CFLAGS ."
 echo "yes"