CONFIG_MODVERSIONS and same named files
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/
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.cexports FOO, anddrivers/b/foo.cexports BAR,include/linux/modules/foo.verwill only have the information aboutdrivers/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.cfs/proc/procfs_syms.cfs/fat/fatfs_syms.cfs/vfat/vfatfs_syms.cfs/lockd/lockd_syms.ckernel/ksyms.cnet/netsyms.cnet/sunrpc/sunrpc_syms.cnet/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.