NetBSD

History

uwe ff265b0443 In binutils 2.16 new SuperH flags were introduced. Since we still use old gdb, teach it new flags, so that it can recognize binaries compiled with new binutils. For new flags set arch to an approximate superset that this version of bfd knows about. This is good enough for gdb. PR port-sh3/32972		2006-03-07 02:16:23 +00:00
..
dist	In binutils 2.16 new SuperH flags were introduced. Since we still use	2006-03-07 02:16:23 +00:00
lib	Now that the libiberty config.h was made MD again, we need to instruct	2006-02-16 10:36:24 +00:00
libexec	Allow for \H -> "address ..." substitution in PIPE ports. Useful	2005-09-07 12:38:16 +00:00
usr.bin	Use MKPRIVATELIB instead of NOLINKLIB/NOMAN/NOPIC/NOLINT.	2006-02-25 12:04:23 +00:00
usr.sbin	. Have dbsym explicitly suggest increasing SYMTAB_SPACE when	2005-11-24 12:54:29 +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.