NetBSD/gnu
dsl b9a6294f9c When compiling with -Os put all strings into .rodata.str1.1 (ie byte aligned)
rather than putting those longer than 30 chars into .rodata.str1.32.
Apparantly gcc 3.4.4 has this change...
In spite of everything being compressed, this saves over 13k in the boot
floppies.
2005-11-05 18:29:53 +00:00
..
dist When compiling with -Os put all strings into .rodata.str1.1 (ie byte aligned) 2005-11-05 18:29:53 +00:00
lib Re-run mknative after the fix to use the correct AS - sparc64 has 2005-05-16 11:16:18 +00:00
libexec Allow for \H -> "address ..." substitution in PIPE ports. Useful 2005-09-07 12:38:16 +00:00
usr.bin Oops, forgot this when switching v9 -> ultrasparc as default -mcpu 2005-10-29 20:40:45 +00:00
usr.sbin Build ncdcs on everything. Allows better set sharing (and we don't exclude 2005-10-27 17:39:35 +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.