[lkml]   [2001]   [Nov]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject2.4.13: unresolved symbols with modules_install
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 /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 ]; then /sbin/depmod -ae -F 2.4.13; fi
depmod: *** Unresolved symbols in
depmod: proc_get_inode

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

Andreas Achtzehn
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:12    [W:0.096 / U:1.480 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site