From 409e2df1f26bbbe299c8cd5111fd17f03595be17 Mon Sep 17 00:00:00 2001 From: "H. Peter Anvin" Date: Tue, 1 Mar 2016 21:53:09 -0800 Subject: [PATCH] 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 --- configure.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure.in b/configure.in index 86d2af92..b7f7110a 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).])