NetBSD/gnu
mycroft b06a300a8a Fix a bug WRT -vomit-frame-pointer -- use_return_insn() must return false if
we saved the GOT pointer register.
Note: This is already fixed in the GCC 3 sources, but GCC 3 uses a different
condition to determine whether to save and restore the register, so the patch
cannot be the same.
2002-09-26 14:21:39 +00:00
..
dist Fix a bug WRT -vomit-frame-pointer -- use_return_insn() must return false if 2002-09-26 14:21:39 +00:00
lib Remove more old toolchain bits. 2002-09-17 23:24:52 +00:00
libexec - use NETBSDSRCDIR as appropriate 2002-09-19 03:09:31 +00:00
usr.bin Re-add, it is still used, but one only sees it in a full build, not a tools 2002-09-22 13:06:44 +00:00
usr.sbin add the -x option to extract the filesystem image from the kernel 2002-09-26 10:40:59 +00:00
Makefile
README Remove completely outdated maintenance history, and add proper NetBSD RCS tag. 2002-09-22 09:47:56 +00:00

README

$NetBSD: README,v 1.4 2002/09/22 09:47:56 wiz 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.