diff options
| author | Dongwon Kim <[email protected]> | 2016-02-16 10:05:24 -0800 |
|---|---|---|
| committer | Matt Turner <[email protected]> | 2016-03-17 16:53:23 -0700 |
| commit | 49eb5e75bdc54d230c87669dacf24efb8217e756 (patch) | |
| tree | e07f0e314ff20216a21a7a066090e81d9bfa7169 /configure.ac | |
| parent | d6b9202873f015174592e32f3325d00c57153d2d (diff) | |
configure.ac: enable_asm=yes when x-compiling across same X86 arch
Currently, configure script is forcing 'enable_asm' to be 'no'
whenever cross-compilation is performed on X86 host. This is
based on an assumption that target architecture is different
from host's (i.e. ARM). But there's always a case that we do
cross-compilation for target that is also X86 based just like
host in which same ASM codes will be supported. 'enable_asm'
should not be forced to be "no" anymore in this case.
v2: corrected commit message
Reviewed-by: Matt Turner <[email protected]>
Signed-off-by: Dongwon Kim <[email protected]>
Diffstat (limited to 'configure.ac')
| -rw-r--r-- | configure.ac | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/configure.ac b/configure.ac index 31703b58301..1ece6fa4e16 100644 --- a/configure.ac +++ b/configure.ac @@ -704,8 +704,10 @@ test "x$enable_asm" = xno && AC_MSG_RESULT([no]) if test "x$enable_asm" = xyes -a "x$cross_compiling" = xyes; then case "$host_cpu" in i?86 | x86_64 | amd64) - enable_asm=no - AC_MSG_RESULT([no, cross compiling]) + if test "x$host_cpu" != "x$target_cpu"; then + enable_asm=no + AC_MSG_RESULT([no, cross compiling]) + fi ;; esac fi |