Skip to contentSkip to conversation

CONFIG_MODVERSIONS and same named files

DISCUSSION Tom Rini 2 participants 2 messages Feb 16, 2001 – Feb 17, 2001

lore
Share & tools
lore

Tom Rini

author
#0 lore raw

Hey all. The modversions code has a slight problem with files of the same name, but in different directories. eg: drivers/a/foo.c exports FOO, and drivers/b/foo.c exports BAR, include/linux/modules/foo.ver will only have the information about drivers/b/foo.c. Anyone got an idea on how to fix this?

Signature · 2 lines
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
#1 lore raw
Quoted 4 lines · Tom Rini

Hey all. The modversions code has a slight problem with files of the same name, but in different directories. eg: drivers/a/foo.c exports FOO, and drivers/b/foo.c exports BAR, include/linux/modules/foo.ver will only have the information about drivers/b/foo.c. Anyone got an idea on how to fix this?

Files that export symbols must have unique names. Which is why we have abominations like this.

fs/msdos/msdosfs_syms.c
fs/proc/procfs_syms.c
fs/fat/fatfs_syms.c
fs/vfat/vfatfs_syms.c
fs/lockd/lockd_syms.c
kernel/ksyms.c
net/netsyms.c
net/sunrpc/sunrpc_syms.c
net/irda/irsyms.c

Module symbol versions is being completely redesigned for 2.5 and will not have this problem. In the meantime create a unique filename for anything that exports symbols.