NetBSD/gnu
mrg 19499f3f8d update all of these makefiles for the .so -> .pico change.
most of them are most harmless, but the libgcc parts are quite essential.
before this change, all the special rules for .pico files were not applied,
and exception handling wasn't enabled.  this caused c++ exceptions not to
work on sparc64.


this fixes the build of boost-headers (it was correctly calling exception
support broken!), which in turn makes all the things that depend upon it
to actually work again on sparc64.
2010-03-14 00:26:09 +00:00
..
dist Use HUGE_VAL on VAX as INFINITY requires a warning according to ISO C99 2010-03-01 00:15:47 +00:00
lib update all of these makefiles for the .so -> .pico change. 2010-03-14 00:26:09 +00:00
usr.bin update all of these makefiles for the .so -> .pico change. 2010-03-14 00:26:09 +00:00
Makefile There's no longer a gnu/usr.sbin so don't try to descend into it. 2009-11-08 17:01:58 +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.