Properly check for AltiVec CFLAGS instead of guessing based on compiler vendor.
authorDiego Biurrun <diego@biurrun.de>
Sat, 15 Mar 2008 15:54:20 +0000 (15:54 +0000)
committerDiego Biurrun <diego@biurrun.de>
Sat, 15 Mar 2008 15:54:20 +0000 (15:54 +0000)
Originally committed as revision 12448 to svn://svn.ffmpeg.org/ffmpeg/trunk

configure

index a2e9574..7a89ab2 100755 (executable)
--- a/configure
+++ b/configure
@@ -1532,12 +1532,9 @@ fi
 
 # AltiVec flags: The FSF version of GCC differs from the Apple version
 if enabled altivec; then
-    if test -n "`$cc -v 2>&1 | grep version | grep Apple`"; then
-        add_cflags "-faltivec"
-    else
-        add_cflags "-maltivec -mabi=altivec"
-        check_header altivec.h
-    fi
+    check_cflags -maltivec -mabi=altivec &&
+        check_header altivec.h ||
+        check_cflags -faltivec
 
     # check if our compiler supports Motorola AltiVec C API
     enabled altivec_h &&