NetBSD

History

thorpej 9022b5f984 In ASM_SPEC: * If -mhard-float is passed to the compiler, pass -mfpa10 to the assembler. * If -msoft-float is passed to the compiler, pass -mfpu=softvfp to the assembler. * If neither -mhard-float nor -msoft-float are passed to the compiler, pass -mfpu=softvfp to the assembler. These changes properly mark objects as using soft-VFP, as is the default code generation for NetBSD ARM ELF.		2002-11-21 17:57:35 +00:00
..
dist	In ASM_SPEC:	2002-11-21 17:57:35 +00:00
lib	Remove more old toolchain bits.	2002-09-17 23:24:52 +00:00
libexec	- use NETBSDSRCDIR as appropriate	2002-09-19 03:09:31 +00:00
usr.bin	Comment out cross-references to man pages that don't exist.	2002-10-31 02:51:06 +00:00
usr.sbin	add missnig -I to gnu/dist/mrouted, which is needed by gcc 3.2	2002-10-17 12:50:00 +00:00
Makefile	Use @true instead of @${TRUE} in includes-foo targets, since there is no	2001-10-12 21:05:08 +00:00
README	Remove completely outdated maintenance history, and add proper NetBSD RCS tag.	2002-09-22 09:47:56 +00:00

README

$NetBSD: README,v 1.4 2002/09/22 09:47:56 wiz 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.