On Sun, 26 Jul 1998 13:45:49 -0700 
 Jonathan Stone <jonathan@DSG.Stanford.EDU> wrote:

 > If they do, it'll break all mips-related uses of ${MACHINE_ARCH} in
 > Makefiles, walking into arch/mips/ sub-directories, set-list
 > construction, tests for ${MACHINE_ARCH} in ONLY_FOR_ARCHES, and so on.

So, if a program is ONLY_FOR_ARCHES mipseb (because say we're running
an SGI binary, hey, it could happen), then my solution works and yours
doesn't.

 > If those get broken I'm very tempted to back it out until they get
 > fixed, so makefile or C-source clients can just test for "mips" or
 > ``#ifdef __mips__'' again.  It's just not as simple as Jason makes out.

Then you're being thick.  Read what I said about the toolchain.  Then think
hard.

Jason R. Thorpe                                       thorpej@nas.nasa.gov
NASA Ames Research Center                            Home: +1 408 866 1912
NAS: M/S 258-5                                       Work: +1 650 604 0935
Moffett Field, CA 94035                             Pager: +1 650 940 5942