NetBSD

History

skrll 95cfd78c59 Updates so that mknative gets the right things. - Disable symbol versioning (for now) - Make sure that libiberty knows its being configured with a cross compiler. - The CXX_* variables are no longer needed/used. - LIB2FUNCS_EXTRA gets pulled in via LIB2ADD - Get LIB1ASMFUNCS and LIB2ASMSRC - MAYBE_USE_COLLECT2 got renamed to USE_COLLECT2 (but might not be used) - Get EXTRA_HEADERS so that we get generate the right paths for CPPFLAGS - Get some variables related to shared libgcc		2004-02-10 09:37:58 +00:00
..
dist	Updates so that mknative gets the right things.	2004-02-10 09:37:58 +00:00
lib	Move libgcc3/*.mk to libgcc3/arch.	2004-01-02 11:58:32 +00:00
libexec	Let "cu" connect at 230400 bps, if the port supports it.	2004-02-03 14:22:26 +00:00
usr.bin	use uname=${BINOWN} gname=${BINGRP} instead of uname=root gname=wheel	2004-02-09 06:52:34 +00:00
usr.sbin	consistency tweaks in .stamp files	2004-02-08 22:28:27 +00:00
Makefile
README

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.