NetBSD/gnu
jmc b5ac9053b4 Redo this rule so it depends on libiberty.a rather than just the directory.
Otherwise an aborted build would cause this to be skipped on MKUPDATE.
Also, run configure w. $HOST_SH as highlighted in PR#25606
2004-06-12 14:59:36 +00:00
..
dist Correct the previous; should have been statvfs for >2.0D. 2004-05-31 03:55:20 +00:00
lib Re-run mknative. 2004-05-25 13:39:35 +00:00
libexec Use MKPRIVATELIB=yes instead of providing an empty libinstall:: target and 2004-05-23 02:24:50 +00:00
usr.bin Redo this rule so it depends on libiberty.a rather than just the directory. 2004-06-12 14:59:36 +00:00
usr.sbin trace.8 duplicated in MAN variable, overriding the MLINK instance. 2004-06-08 23:30:00 +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.