Assar Westerlund <[EMAIL PROTECTED]> writes:
> Mo DeJong <[EMAIL PROTECTED]> writes:
>> Can we at least get agreement that this AC_C_BIGENDIAN macro is in
>> fact broken?
> I think so. But it's really hard to figure out the endianess of another
> machine. The only ways of doing that that I can think of is to add a
> table, have explicit options, or if we can find out from the include
> files (typically sys/endian.h).
I don't remember now where I originally read this (I thought it was in the
autoconf manual, but I can't find it now), but I seem to recall that the
theory behind the autoconf endianness test was that it could fail to
decide and that any program that could be cross-compiled and cared about
endianness had to be prepared to test endianness at run-time. Which would
imply that it should be possible to use the AC_C_BIGENDIAN macro with a
package that supports cross-compilation and have it return some sort of
indeterminate result.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
