On Fri, 20 Jul 2001, Izumi Tsutsui wrote:

: > 	gnusrc/gnu/lib/libiberty/arch/mipsel: config.h defs.mk

: Ugh, do we have to have both mipsel and mipseb directories for this?

Yes.

The reason for this is that the toolchain needs, at its top configure level,
to know the *default platform*.  MIPS isn't both endiannesses at once, so
pick one as the default, mipsel or mipseb.  :)

So, it is much easier to have the stubs generated for mipseb and mipsel
separately, and deal with it that way.  The toolchain2netbsd script is
designed to be easy to use; just run it and commit.

It's possible that some things will get merged back to MI status, such as
the definitions used for libiberty, once this is all ironed out.  But for
real target-dependent bits such as gcc, gdb, bfd, and binutils, you *do*
need to know the difference between mipsel and mipseb for generated *.h
files.

-- 
-- Todd Vierling <tv@wasabisystems.com>  *  Wasabi NetBSD:  Run with it.
-- NetBSD 1.5 now available on CD-ROM  --  http://www.wasabisystems.com/