NetBSD/gnu
skrll b5d3cf6021 Complete the fix for PR 22452 by doing the same thing as stock gcc. That
is, use the symbol versioning script to remove certain symbols from the
dynamic symbol table.

Do the symbol versioning thing for all platforms.

Whilest our ld.elf_so(1) doesn't understand symbol versioning this
doesn't matter as all the exposed symbols appear unversioned until symbol
versioning support is added (if ever).
2004-07-05 12:27:41 +00:00
..
dist Complete the fix for PR 22452 by doing the same thing as stock gcc. That 2004-07-05 12:27:41 +00:00
lib Complete the fix for PR 22452 by doing the same thing as stock gcc. That 2004-07-05 12:27:41 +00:00
libexec Add missing NetBSD ID tags 2004-06-30 03:26:26 +00:00
usr.bin Redo the layout here by moving man stuff into a subdir. This is only needed here 2004-06-24 04:38:29 +00:00
usr.sbin trace.8 duplicated in MAN variable, overriding the MLINK instance. 2004-06-08 23:30:00 +00:00
Makefile Install the MMX/SSE/Altivec include files that gcc provides. 2003-12-05 18:56:11 +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.