From 47c45fbb453819fb2f4885d8abdb0db2ea87adde Mon Sep 17 00:00:00 2001 From: Hermet Park Date: Thu, 4 Aug 2016 15:43:41 +0900 Subject: [PATCH] efl: fix a neon build break. We found a some build break problem due to a build system. In efl configuration, our efl configure enables neon if it's available, but neon gonna partially turned off on evas compilation if the build system has a non neon CFLAG option (ie, mfpu=vfpv..). In the end, neon is partially enabled and it turns out a build break. It's non-sense but we can't allow this breakage. There is no way to ignore build system option nor override our neon option perfectly, so, Let efl package ruled by build system overall. http://git.enlightenment.org/core/efl.git/commit/?id=77d2e0cb959b9e7ecc6ffc09b67031ac3687f332 Change-Id: Ie94e277b206830a517a4fb33f1187b1fa785d243 --- configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index e9e29ae69e..574193303f 100755 --- a/configure.ac +++ b/configure.ac @@ -563,7 +563,7 @@ case $host_cpu in build_cpu_neon="yes" AC_MSG_CHECKING([whether to use NEON instructions]) CFLAGS_save="${CFLAGS}" - CFLAGS="${CFLAGS} -mfpu=neon -ftree-vectorize" + CFLAGS="-mfpu=neon -ftree-vectorize ${CFLAGS}" AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[#include ]], [[asm volatile ("vqadd.u8 d0, d1, d0\n")]])],[ AC_MSG_RESULT([yes]) AC_DEFINE([BUILD_NEON], [1], [Build NEON Code]) -- 2.34.1