4c92852a80
we're ELF now, and there are many missing checks against OBJECT_FMT. if we ever consider switching, the we can figure out what new ones we need but for now it's just clutter. this doesn't remove any of the support for exec_aout or any actually required-for-boot a.out support, only the ability to build a netbsd release in a.out format. ie, most of this code has been dead for over a decade. i've tested builds on vax, amd64, i386, mac68k, macppc, sparc, atari, amiga, shark, cats, dreamcast, landisk, mmeye and x68k. this covers the 5 MACHINE_ARCH's affected, and all the other arch code touched. it also includes some actual run-time testing of sparc, i386 and shark, and i performed binary comparison upon amiga and x68k as well. some minor details relevant: - move shlib.[ch] from ld.aout_so into ldconfig proper, and cut them down to only the parts ldconfig needs - remove various unused source files - switch amiga bootblocks to using elf2bb.h instead of aout2bb.h |
||
---|---|---|
.. | ||
dist | ||
lib | ||
usr.bin | ||
Makefile | ||
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.