To summarize: the code assumes host-platform to be 8-bit ebcdic
or 8-bit ascii. target-platform has 16-bit per short. This is the setup of
everyone who runs cross-compilers these days AFAIK. The test should explicitly
check that one answer has been found (neither zero nor two) and otherwise
fail just like the current AC_C_BIGENDIAN does. This case of one amongst
a million would enforce the autoconf'ed package installer to go without
autoconf'ed configure, whereas that is the case we have now for
*everyone* trying to cross-compile packages containing AC_C_BIGENDIAN.
Now, would the code have a chance to go into main' autoconf anyway,
or better leave it to some AC_C_BIGENDIAN_CROSS in the autoconf-archive...
Guido Draheim wrote:
> that happen... hmm... unicode-only host-platform? Anybody seen that? It
> seems I am locked to much with the 20 platforms I have around me... ;-)
