NetBSD/gnu
lukem 25d2de94fe Document what BROKEN_SPOOLER_FLAGS 'add 16' is for, and add it to the
default broken flags.  groff 1.19 defaulted to this value off, whereas
groff 1.18.1 and earlier defaulted to this being on.  Setting this value
fixes postscript printing to my HP LJ4m.
Note: BROKEN_SPOOLER_FLAGS was previously `7', so we were already enabling
workarounds for other issues...
2004-01-27 01:00:09 +00:00
..
dist Don't run commit_prep UNSETXID in server mode, because the created #cvs.lastdir 2004-01-24 23:46:30 +00:00
lib Move libgcc3/*.mk to libgcc3/arch. 2004-01-02 11:58:32 +00:00
libexec Rework how MAKEVERBOSE operates: 2003-10-21 10:01:19 +00:00
usr.bin Document what BROKEN_SPOOLER_FLAGS 'add 16' is for, and add it to the 2004-01-27 01:00:09 +00:00
usr.sbin support MKDOC=no 2004-01-12 01:33:51 +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.