On Sun, 9 Dec 2001, Matthew Fredette wrote:

: The m68000 needs a libgcc.a, and I take it no other new-toolchain
: MACHINE_ARCHs do, on account of this in src/tools/toolchain/Makefile:
:
: MAKE_ARGS=	MACHINE= \
: 		LIBGCC= LIBGCC1= LIBGCC1_TEST= LIBGCC2= INSTALL_LIBGCC=

This is deliberate; there is no need to create libgcc.a in the *compiler's*
directory, because it will never get used.  All builds with the new
toolchain have DESTDIR set, which means that -nostdlib (and an absolute path
to ${DESTDIR}/usr/lib/libgcc.a) will be used.  (This avoids the
chicken-and-egg problem that you found where libgcc2.c wants to get at the
native target headers.)

What needs to work properly for you is src/gnu/lib/libgcc, since that's the
only libgcc that will be used for a build.

-- 
-- Todd Vierling <tv@wasabisystems.com>  *  Wasabi & NetBSD:  Run with it.
-- CDs, Integration, Embedding, Support -- http://www.wasabisystems.com/