diff options
| author | Hermet Park <hermet@hermet.pe.kr> | 2016-08-04 15:22:23 +0900 |
|---|---|---|
| committer | Hermet Park <hermet@hermet.pe.kr> | 2016-08-04 15:39:51 +0900 |
| commit | 77d2e0cb959b9e7ecc6ffc09b67031ac3687f332 (patch) | |
| tree | ad5aac4a0fb05ccda26ed62580f1e01b6efbda3f | |
| parent | d458101a410a6ffc92d2e59f920a6246f833999f (diff) | |
| download | efl-77d2e0cb959b9e7ecc6ffc09b67031ac3687f332.tar.gz | |
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.
| -rw-r--r-- | configure.ac | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/configure.ac b/configure.ac index 8cb7cd4ea7..cb89323ec0 100644 --- a/configure.ac +++ b/configure.ac @@ -593,7 +593,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 <arm_neon.h>]], [[asm volatile ("vqadd.u8 d0, d1, d0\n")]])],[ AC_MSG_RESULT([yes]) AC_DEFINE([BUILD_NEON], [1], [Build NEON Code]) |