NetBSD/gnu
mrg 099de62e9e new configurations for all supported platforms tested and known working
on these platforms so far:
	- alpha, arm, i386, mipseb, mipsel, sparc64
built but not yet tested on:
	- armeb, sparc, amd64
build errors (mostly not related) on:
	- hppa, m68000, m68k, macppc, sh3el, sh3eb, vax

XXX again this is not everything required; many other changes in
XXX already used files are left out.
2003-12-03 06:53:48 +00:00
..
dist include "getopt.h" as we refer to struct option. 2003-11-27 13:52:30 +00:00
lib don't build libopcodes/bfd/iberty here if we have binutils 2.14 2003-11-27 13:53:11 +00:00
libexec Rework how MAKEVERBOSE operates: 2003-10-21 10:01:19 +00:00
usr.bin new configurations for all supported platforms tested and known working 2003-12-03 06:53:48 +00:00
usr.sbin find libraries etc in a binutils 2.14 world. 2003-11-27 14:36:45 +00:00
Makefile Make "make includes" descend into the sendmail tree. 2003-07-04 04:53:50 +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.