NetBSD

History

uwe 562404165e Copy .s.so rule we use for libgcc_pic to make sure the millicode is .hidden in libgcc_s.so as well. Enable it for sh3. Other CPUs for which gcc uses millicode probably need this too. Per discussion with Nick Hudson <skrll>.		2004-04-28 01:44:59 +00:00
..
dist	Fix botched merge	2004-04-27 05:35:12 +00:00
lib	Copy .s.so rule we use for libgcc_pic to make sure the millicode is	2004-04-28 01:44:59 +00:00
libexec	Replace the statfs() family of system calls with statvfs().	2004-04-21 01:05:31 +00:00
usr.bin	Drop workaround for toolchain/22489 now that the fix for it has been pulled	2004-04-26 09:17:16 +00:00
usr.sbin	Add readmes &/ obsoletes that I missed.	2004-04-27 15:35:55 +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.