From: "David S. Miller" <davem@redhat.com>
To: Jeff Layton <jtlayton@bigfoot.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: unresolved symbols on SPARC with depmod -ae
Date: Thu, 5 Apr 2001 05:28:02 -0700 (PDT) [thread overview]
Message-ID: <15052.25810.619907.25595@pizda.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0104050804120.26901-100000@kaitan.hacknslash.net>
In-Reply-To: <Pine.LNX.4.21.0104050804120.26901-100000@kaitan.hacknslash.net>
Jeff Layton writes:
> Anyway here's what I get, should I be concerned about this?
...
> caladan:~# /sbin/depmod -ae -F /boot/System.map-2.4.2
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.2/kernel/drivers/block/loop.o
> depmod: .div
> depmod: .urem
> depmod: .umul
> depmod: .udiv
> depmod: .rem
> depmod: *** Unresolved symbols in
Try to load one of the modules which show the problem, does
it work? If so, it is a bug in depmod's handling of these
".foo" symbols.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-04-05 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-05 12:14 Jeff Layton
2001-04-05 12:28 ` David S. Miller [this message]
2001-04-05 12:32 ` Jeff Layton
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=15052.25810.619907.25595@pizda.ninka.net \
--to=davem@redhat.com \
--cc=jtlayton@bigfoot.com \
--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®