[nasm:master] configure.in: if byte order is unknown or ill defined, don't define any

[nasm-bot f. H. P. A. <hp...@zy...>]

Commit-ID:  ef63588eb483f96550d5a6d097363ff6e7a733f4
Gitweb:     http://repo.or.cz/w/nasm.git?a=commitdiff;h=ef63588eb483f96550d5a6d097363ff6e7a733f4
Author:     H. Peter Anvin <hp...@zy...>
AuthorDate: Tue, 1 Mar 2016 21:53:09 -0800
Committer:  H. Peter Anvin <hp...@zy...>
CommitDate: Tue, 1 Mar 2016 21:53:09 -0800

configure.in: if byte order is unknown or ill defined, don't define any

We can always operate correctly if neither WORDS_BIGENDIAN nor
WORDS_LITTLEENDIAN are defined, so if the word order is either
indeterminable or universal (the compiler generates both bigendian and
litteendian output from the same sources) then define neither.

Signed-off-by: H. Peter Anvin <hp...@zy...>


---
 configure.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configure.in b/configure.in
index e13eeff..a4b52d0 100644
--- a/configure.in
+++ b/configure.in
@@ -67,7 +67,7 @@ AC_C_CONST
 AC_C_INLINE
 AC_C_RESTRICT
 AC_TYPE_SIZE_T
-AC_C_BIGENDIAN(AC_DEFINE(WORDS_BIGENDIAN),AC_DEFINE(WORDS_LITTLEENDIAN))
+AC_C_BIGENDIAN(AC_DEFINE(WORDS_BIGENDIAN),AC_DEFINE(WORDS_LITTLEENDIAN),,)
 AH_TEMPLATE(WORDS_BIGENDIAN,
 [Define to 1 if your processor stores words with the most significant
 byte first (like Motorola and SPARC, unlike Intel and VAX).])