Subject: depmod: unresolved symbol(s) (Was: What's compiled into the kernels ...)
From: Paul J. Lucas (pjl@barefooters.org)
Date: Sun Mar 12 2000 - 23:20:55 MST
On Sat, 11 Mar 2000, I wrote:
> I decided to build my own kernel. ... It took a couple of tries, but
> it works now ...
Almost... I get unresolved symbol(s) errors upon booting or
doing a depmod, i.e.:
# depmod -ae
/lib/modules/2.2.15-2.8.0/fs/lockd.o: unresolved symbol(s)
do_lockdctl
/lib/modules/2.2.15-2.8.0/misc/mouse.o: unresolved symbol(s)
adb_mouse_interrupt
Yes, before installing the new modules, I deleted the old set so
they aren't left over from previous builds.
The definition of do_lockdctl appears in fs/filesystems.c. If I
do:
ksyms -a | grep do_lockdctl
I get:
c0132540 do_lockdctl_R__ver_do_lockdctl
The definition of adb_mouse_interrupt appears in
drivers/char/adbmouse.c. It does not appear in ksyms at all even
though I specifically did a CONFIG_ADBMOUSE=y in my config file
(so it should be built into the kernel).
Help.
- Paul
P.S.: When building a kernel, is it OK to "strip vmlinux"
before installation?
This archive was generated by hypermail 2a24 : Sun Apr 02 2000 - 21:09:31 MDT