2.5.52: Many, many unresolved symbols!?

2.5.52: Many, many unresolved symbols!?

[axel]

[-- Attachment #1: Type: text/plain, Size: 603 bytes --]

Hi,

after kernel build of 2.5.52-bk4 snapshot, depmod results in a very long
list of unresolved symbols.

if [ -r System.map ]; then /sbin/depmod -ae -F System.map  2.5.52bk4; fi
depmod: *** Unresolved symbols in
/lib/modules/2.5.52bk4/kernel/drivers/block/floppy.ko
...
...
...

I see it! All the listed files that have unresolved symbols end in .ko ?!
I believe that's not ok.


I have attached the bzipped output.

Best regards,
Axel Siebenwirth



#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
CONFIG_KMOD=y

[-- Attachment #2: build.log.bz2 --]
[-- Type: application/octet-stream, Size: 3452 bytes --]

Re: 2.5.52: Many, many unresolved symbols!?

[Alex Goddard]

On Fri, 20 Dec 2002 axel@pearbough.net wrote:

> Hi,
> 
> after kernel build of 2.5.52-bk4 snapshot, depmod results in a very long
> list of unresolved symbols.
> 
> if [ -r System.map ]; then /sbin/depmod -ae -F System.map  2.5.52bk4; fi
> depmod: *** Unresolved symbols in
> /lib/modules/2.5.52bk4/kernel/drivers/block/floppy.ko

Make sure you have the latest module-init-tools installed, and that 
/sbin/depmod points to the newest version of depmod from the 
module-init-tools package you just (re)installed.

-- 
Alex Goddard
agoddard@purdue.edu