mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Achtzehn <linux-kernel@achtzehn.2y.net>
To: linux-kernel@vger.kernel.org
Subject: 2.4.13: unresolved symbols with modules_install
Date: Sat, 3 Nov 2001 15:48:18 +0100	[thread overview]
Message-ID: <01110315481802.06645@paris> (raw)

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

             reply	other threads:[~2001-11-03 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-03 14:48 Andreas Achtzehn [this message]
2001-11-04  1:52 ` Keith Owens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=01110315481802.06645@paris \
    --to=linux-kernel@achtzehn.2y.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®