From 4477b9f4243d88368917b40873295d3b8f05bbef Mon Sep 17 00:00:00 2001
From: Diego Biurrun <diego@biurrun.de>
Date: Sat, 15 Mar 2008 15:54:20 +0000
Subject: Properly check for AltiVec CFLAGS instead of guessing based on
 compiler vendor.

Originally committed as revision 12448 to svn://svn.ffmpeg.org/ffmpeg/trunk
---
 configure | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

(limited to 'configure')

diff --git a/configure b/configure
index a2e95747e8..7a89ab2516 100755
--- 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 &&
-- 
cgit v1.2.3