CONFIG_MODVERSIONS and same named files

CONFIG_MODVERSIONS and same named files

[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?

-- 
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

Re: CONFIG_MODVERSIONS and same named files

[Keith Owens]

On Fri, 16 Feb 2001 08:19:28 -0700, 
Tom Rini <trini@kernel.crashing.org> wrote:
>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.