c566d4623b
- Enable installing binutils from the base system. - Import texinfo which is required for the binutils tools to be compiled. - Also adapted the fetch rules to correctly generate the gitignore files for gcc, and allow the case of multiple modules in the same directory, as found in gnu/dist. Warning: This patch has an entry in docs/UPDATING Change-Id: Ib781734e8fd7f9c6265fa65d62ba2cf3fccbc5ba
35 lines
1.2 KiB
Plaintext
35 lines
1.2 KiB
Plaintext
$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.
|