summaryrefslogtreecommitdiffstats
path: root/configure
diff options
context:
space:
mode:
authordiego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2>2008-07-26 12:26:04 +0000
committerdiego <diego@b3059339-0415-0410-9bf9-f77b7e298cf2>2008-07-26 12:26:04 +0000
commitd1dcbd2f87335437544484b16f933d520e5d38f3 (patch)
tree45f435b11108781fca3489f3c7f02279ca274f44 /configure
parent1d0ab0131227d9e34b7e9f19d6e861ad495d5441 (diff)
downloadmpv-d1dcbd2f87335437544484b16f933d520e5d38f3.tar.bz2
mpv-d1dcbd2f87335437544484b16f933d520e5d38f3.tar.xz
Remove AltiVec vector declaration compiler compatibility macros.
The original problem was that FSF and Apple gcc used a different syntax for vector declarations, i.e. {} vs. (). Nowadays Apple gcc versions support the standard {} syntax and versions that support {} are available on all relevant Mac OS X versions. Thus the greater compatibility is no longer worth cluttering the code with macros. git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@27350 b3059339-0415-0410-9bf9-f77b7e298cf2
Diffstat (limited to 'configure')
-rwxr-xr-xconfigure7
1 files changed, 2 insertions, 5 deletions
diff --git a/configure b/configure
index 63eb286e27..e540053970 100755
--- a/configure
+++ b/configure
@@ -2470,11 +2470,9 @@ EOF
# check if the compiler supports braces for vector declarations
cat > $TMPC << EOF
$inc_altivec_h
-#define AVV(x...) {x}
-int main(void) { (vector int) AVV(1); return 0; }
+int main(void) { (vector int) {1}; return 0; }
EOF
- cc_check $_altivec_gcc_flags &&
- _def_altivec_vector_braces='#define HAVE_ALTIVEC_VECTOR_BRACES 1'
+ cc_check $_altivec_gcc_flags || die "You need a compiler that supports {} in AltiVec vector declarations."
# Disable runtime cpudetection if we cannot generate AltiVec code or
# AltiVec is disabled by the user.
@@ -8630,7 +8628,6 @@ $_def_gethostbyname2
`ff_config_enable "$_cpuexts_all" "$_cpuexts" "HAVE"`
$_def_altivec_h // enables usage of altivec.h
-$_def_altivec_vector_braces
/* libvo options */
#define SCREEN_SIZE_X 1