NetBSD

History

nathanw 99922845b9 Include both application threads and "raw" LWPs in GDB's list of threads. This is useful for a variety of things, including examing the internal state of the thread library when things are going wrong there. Currently only works on core files; both ptrace and gdb will need a bit more work before this will be useful on live processes. Inspired by the similar behavior of the Solaris thread module.		2003-02-17 20:32:04 +00:00
..
dist	Include both application threads and "raw" LWPs in GDB's list of	2003-02-17 20:32:04 +00:00
lib	do not install libioP.h nor iostreamP.h	2003-01-28 14:40:59 +00:00
libexec	Use a neutral error message - the details have been printed already, and	2003-01-21 22:47:20 +00:00
usr.bin	Add IDIST variable to avoid having to duplicate paths.	2003-02-14 08:25:36 +00:00
usr.sbin	allow NO_SENDMAIL to equal "no"	2003-01-09 16:57:45 +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.