NetBSD/gnu
thorpej 1d99a54efe Bring in the following patch from FSF binutils mainline:
2003-06-13  Richard Earnshaw  <rearnsha@arm.com>

	* tc-arm.c (FPU_DEFAULT, case TE_LINUX): Default to FPU_ARCH_FPA.
	(FPU_DEFAULT, case TE_NetBSD): Default to FPU_ARCH_VFP for ELF,
	FPU_ARCH_FPA for AOUT.
	(md_begin): Don't try to guess the floating point architecture from
	the CPU if the OS ABI (Linux, NetBSD) mandates a particular form.

...per Richard's suggestion.
2003-06-14 16:02:57 +00:00
..
dist Bring in the following patch from FSF binutils mainline: 2003-06-14 16:02:57 +00:00
lib * If MKGCC == no, don't build this library, which is bundled with the 2003-06-01 02:09:31 +00:00
libexec possible scanf overrun 2003-05-17 15:05:19 +00:00
usr.bin Re-remove admin, port-arm32. 2003-05-30 13:42:18 +00:00
usr.sbin Now that <bsd.prog.mk> DTRT if HOSTPROG is defined (i.e, it is a no-op), 2003-05-18 07:57:31 +00:00
Makefile
README

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.