Commit-ID: 409e2df1f26bbbe299c8cd5111fd17f03595be17
Gitweb: http://repo.or.cz/w/nasm.git?a=commitdiff;h=409e2df1f26bbbe299c8cd5111fd17f03595be17
Author: H. Peter Anvin <hp...@zy...>
AuthorDate: Tue, 1 Mar 2016 21:53:09 -0800
Committer: H. Peter Anvin <hp...@zy...>
CommitDate: Fri, 4 Mar 2016 11:11:37 -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.
>From master branch checkin ef63588eb483f96550d5a6d097363ff6e7a733f4
Resolved Conflicts:
configure.in
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 86d2af9..b7f7110 100644
--- a/configure.in
+++ b/configure.in
@@ -67,7 +67,7 @@ AC_C_INLINE
AC_C_RESTRICT
AC_TYPE_SIZE_T
PA_WORKING_BOOL
-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).])
|