Peter Wemm 62c10d2dcb symorder appears to have been designed to run on executable files ... only, as it payes no attention to the relocation table (which references the symbols). As a result, running "symorder -c" to clean up the visibility of a LKM ".o" file (as is done in the new bsd.kmod.mk) totally screws up the relocation table, making the LKM file unloadable. (ld: bogus relocation record) This is a pretty crude fix - I've changed symorder so that when running in "cleanup" mode, it disables the reordering which was screwing up the relocation table. I'm sure there is a better fix, but I didn't have the energy. Feel free to fix this hack, probably by renumbering the symbol indexes in the relocation table.		1995-10-28 12:27:20 +00:00
..
Makefile	Initial import, 0.1 + pk 0.2.4-B1	1993-06-12 14:49:13 +00:00
symorder.1	Add a '-c' option for cleaning namelists of various things.	1995-10-15 14:31:10 +00:00
symorder.c	symorder appears to have been designed to run on executable files	1995-10-28 12:27:20 +00:00