summaryrefslogtreecommitdiffstats
path: root/lkm
diff options
context:
space:
mode:
authorpeter <peter@FreeBSD.org>1995-10-28 12:27:20 +0000
committerpeter <peter@FreeBSD.org>1995-10-28 12:27:20 +0000
commit466353d34a79d4d0e9ee249600e9424f3bc90d9f (patch)
tree99dd342e5f784eac91e7c9aca0f37f8d3da7a548 /lkm
parent449a77b65000fd376fbcba537e5fbbba005dae63 (diff)
downloadFreeBSD-src-466353d34a79d4d0e9ee249600e9424f3bc90d9f.zip
FreeBSD-src-466353d34a79d4d0e9ee249600e9424f3bc90d9f.tar.gz
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.
Diffstat (limited to 'lkm')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud