summaryrefslogtreecommitdiffstats
path: root/configure
diff options
context:
space:
mode:
authordiego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2>2008-05-10 14:57:13 +0000
committerdiego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2>2008-05-10 14:57:13 +0000
commit1290235b5899dc94cdb321a6fa31b600fd953acd (patch)
treef0a50e1d0d1ae05ba6457620356a769f2a33de2f /configure
parentb77add3447cb5814feaf1ef26f124c6e00b11eb2 (diff)
downloadmpv-1290235b5899dc94cdb321a6fa31b600fd953acd.tar.bz2
mpv-1290235b5899dc94cdb321a6fa31b600fd953acd.tar.xz
Prefer FSF-style AltiVec flags over Apple-style.
FSF gcc is better than Apple gcc. git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@26720 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'configure')
-rwxr-xr-xconfigure6
1 files changed, 2 insertions, 4 deletions
diff --git a/configure b/configure
index b97e1901d9..c6d649deed 100755
--- a/configure
+++ b/configure
@@ -2418,11 +2418,9 @@ if test "$_altivec" = yes || test "$_runtime_cpudetection" = yes ; then
cat > $TMPC << EOF
int main(void) { return 0; }
EOF
- # check for Darwin-style flags first, since gcc-3.3 (August Update
- # from Apple) on MacOS 10.2.8 accepts but ignores FSF-style flags...
- cc_check -faltivec && _altivec_gcc_flags=-faltivec \
- || cc_check -maltivec -mabi=altivec \
+ cc_check -maltivec -mabi=altivec \
&& _altivec_gcc_flags="-maltivec -mabi=altivec" \
+ || cc_check -faltivec && _altivec_gcc_flags=-faltivec \
|| _altivec=no
echores "$_altivec_gcc_flags"