NetBSD

History

christos 924b906d65 Only compile 64 bit relocations if we can build a 64 bit target (BFD64) not if the 64 bit type is defined (BFD_HOST_64_BIT) because the second is always defined, even if it falls back to a 32 bit type. In our case, this was not the problem; the problem was that we bfd_vma is a 32 bit type when BFD64 is not defined, so the shift was out of range.		2004-12-11 08:42:55 +00:00
..
dist	Only compile 64 bit relocations if we can build a 64 bit target (BFD64)	2004-12-11 08:42:55 +00:00
lib	Regen w. latest mknative to fix ./object.o problems	2004-12-11 07:42:57 +00:00
libexec	Add (unsigned char) cast to ctype functions	2004-11-05 19:56:34 +00:00
usr.bin	run mknative for binutils 2.15 for amd64.	2004-12-11 01:41:25 +00:00
usr.sbin	add postconf.5.html OVERVIEW.html	2004-09-07 23:56:08 +00:00
Makefile	Install the MMX/SSE/Altivec include files that gcc provides.	2003-12-05 18:56:11 +00:00
README	netbsd.org -> NetBSD.org	2003-12-04 23:32:37 +00:00

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.