NetBSD/gnu
mrg 16c4e2e447 generate new libobjc4 files and regenerate many many others.
XXX: re-running "make native-gcc" some times causes the
XXX: gcc/configure test for COMDAT groups to fail.  a fresh
XXX: configure (ie, with no objdir/.native tree yet) seems to
XXX: fix this.  right now mipsel and alpha have the wrong
XXX: definition in the checked in auto-host.h.
2006-05-24 21:20:32 +00:00
..
dist in the NETBSD_NATIVE case, don't set a default GCC_EXEC_PREFIX. just add 2006-05-24 20:52:14 +00:00
lib generate new libobjc4 files and regenerate many many others. 2006-05-24 21:20:32 +00:00
libexec Fix uninitialized variable. 2006-05-13 23:49:02 +00:00
usr.bin generate new libobjc4 files and regenerate many many others. 2006-05-24 21:20:32 +00:00
usr.sbin Add AAAREADME and DB_README. Keep html files in sync. 2006-04-22 16:04:25 +00:00
Makefile Install the MMX/SSE/Altivec include files that gcc provides. 2003-12-05 18:56:11 +00:00
README netbsd.org -> NetBSD.org 2003-12-04 23:32:37 +00:00

README

$NetBSD: README,v 1.5 2003/12/04 23:32:37 keihan Exp $

Organization of Sources:

This directory hierarchy is using a new organization that
separates the GNU sources from the BSD-style infrastructure
used to build the GNU sources.  The GNU sources are kept in
the standard GNU source tree layout under:

	dist/*

The build infrastructure uses the normal BSD way under:

	lib/*
	usr.bin/*

The makefiles in the above hierarchy will "reach over" into
the GNU sources (src/gnu/dist) for everything they need.


Maintenance Strategy:

The sources under src/gnu/dist are generally a combination of
some published distribution plus changes that we submit to the
maintainers and that are not yet published by them.  There are
a few files that are never expected to be submitted to the FSF,
(i.e. BSD-style makefiles and such) and those generally should
stay in src/gnu/lib or src/gnu/usr.bin (the BSD build areas).

Make sure all changes made to the GNU sources are submitted to
the appropriate maintainer, but only after coordinating with the
NetBSD maintainers by sending your proposed submission to the
<tech-toolchain@NetBSD.org> mailing list.  Only send the changes
to the third-party maintainers after consensus has been reached.