Hi Diego,
On Jun 12, 2017 3:53 PM, "Diego Biurrun" <[email protected]> wrote:
---
configure | 24 +++++++-----------------
1 file changed, 7 insertions(+), 17 deletions(-)
diff --git a/configure b/configure
index e8ecf30..46859b7 100755
--- a/configure
+++ b/configure
@@ -4458,29 +4458,19 @@ elif enabled ppc; then
check_cflags -maltivec -mabi=altivec
# check if our compiler supports Motorola AltiVec C API
- check_cc <<EOF || disable altivec
-#include <altivec.h>
-int main(void) {
- vector signed int v1 = (vector signed int) { 0 };
- vector signed int v2 = (vector signed int) { 1 };
- v1 = vec_add(v1, v2);
- return 0;
-}
-EOF
+ check_code cc altivec.h "vector signed int v1 = (vector signed
int) { 0 };
+ vector signed int v2 = (vector signed
int) { 1 };
+ v1 = vec_add(v1, v2);" ||
+ disable altivec
enabled altivec || warn "Altivec disabled, possibly missing --cpu
flag"
fi
if enabled vsx; then
check_cflags -mvsx &&
- check_cc <<EOF || disable vsx
-#include <altivec.h>
-int main(void) {
- int v[4] = { 0 };
- vector signed int v1 = vec_vsx_ld(0, v);
- return 0;
-}
-EOF
+ check_code cc altivec.h "int v[4] = { 0 };
+ vector signed int v1 = vec_vsx_ld(0, v);"
||
+ disable vsx
fi
if enabled power8; then
--
Traditionally, modifying tests like this have been brittle for us -- has it
had a spin on ORACLE? If not would you mind doing so?
No real opinions from me about the Apple GCC patch.
-- Sean McG.
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
