NetBSD

History

matt 58ca788453 Make GCC define __ARM_PCS and __ARM_PCS_VFP as defined by the ARM C Language Extentions (clang already defines them): __ARM_PCS is defined to 1 if the default procedure calling standard for the translation unit conforms to the "base PCS" defined in [AAPCS]. __ARM_PCS_VFP is defined to 1 if the default is to pass floating-point parameters in hardware floating-point registers using the "VFP variant PCS" defined in [AAPCS].		2013-01-25 08:31:43 +00:00
..
dist	Make GCC define __ARM_PCS and __ARM_PCS_VFP as defined by the ARM C Language	2013-01-25 08:31:43 +00:00
lib	do not build profiling versions of libgcc or libgcc_eh.	2011-10-17 14:20:54 +00:00
usr.bin	Set GNATS_ADDR to gnats-bugs@NetBSD.org, like in all other places.	2012-12-21 09:40:17 +00:00
Makefile	Remove the do-external-lib and do-gnu-lib targets, along with	2010-12-03 21:38:46 +00:00
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.