2.4.13: unresolved symbols with modules_install

2.4.13: unresolved symbols with modules_install

[Andreas Achtzehn]

Dear list readers,

I have severe problems compiling a 2.4.13 kernel on a LFS based system. (gcc 
2.95.2, glibc 2.2.4)
For those who have not yet used a LFS system: I have a fully running 
linux-system on a partition. I do the following before compiling the kernel

mount -t proc proc /mnt2/proc
chroot /mnt2 /usr/bin/env -i HOME=/root TERM=$TERM /bin/bash --login

I follow this way to compile a kernel for my system:

tar xvfz linux-2.4.13.tar.gz
cd linux
cp ../config.aktuell ./.config # this is a config I created before
make menuconfig # no changes, just exit (otherwise no autoconfig.h)
make dep 
make clean
make bzImage # works quite well up to here
cp System.map /boot
make modules
make modules_install 

The modules_install ends with 

mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map  2.4.13; fi
depmod: *** Unresolved symbols in 
/lib/modules/2.4.13/kernel/drivers/net/wan/comx.o
depmod:         proc_get_inode
achtzehn:/usr/src/linux#       

Is it possible that this is due to the proc-system and its unusual mounting?

Regards,
Andreas Achtzehn

Re: 2.4.13: unresolved symbols with modules_install

[Keith Owens]

On Sat, 3 Nov 2001 15:48:18 +0100, 
Andreas Achtzehn <linux-kernel@achtzehn.2y.net> wrote:
>/lib/modules/2.4.13/kernel/drivers/net/wan/comx.o
>depmod:         proc_get_inode

The comx.c code is wrong, it is still using an old interface.  This
problem has existed for months, nobody wants to fix it.  Turn off
CONFIG_COMX.