configure.in: if byte order is unknown or ill defined, don't define any
commit409e2df1f26bbbe299c8cd5111fd17f03595be17
authorH. Peter Anvin <hpa@zytor.com>
Wed, 2 Mar 2016 05:53:09 +0000 (1 21:53 -0800)
committerH. Peter Anvin <hpa@zytor.com>
Fri, 4 Mar 2016 19:11:37 +0000 (4 11:11 -0800)
tree3bcae9169e085053b841ffbcd0da896f2c88bec7
parentd414e5f4cdbc9235771d27c942aea3c428221fca
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 <hpa@zytor.com>
configure.in