From: "Bob Piatek" <bobtek@fishcamp.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Cc: "'Tom Rini'" <trini@kernel.crashing.org>
Subject: RE: unresolved symbol
Date: Mon, 31 Dec 2001 16:47:30 -0800 [thread overview]
Message-ID: <000601c1925d$e4bcd940$a2341204@P4> (raw)
In-Reply-To: <20011231230158.GL28513@cpe-24-221-152-185.az.sprintbbd.net>
OK. I updated the modutils package and that fixed it! Thanks so much.
Bob
fishcamp engineering
105 W. Clark Ave
Orcutt, CA 93455
TEL: 805-937-6365
FAX: 805-937-6252
-----Original Message-----
From: Tom Rini [mailto:tmrini@cpe-24-221-152-185.az.sprintbbd.net] On
Behalf Of Tom Rini
Sent: Monday, December 31, 2001 3:02 PM
To: Bob Piatek
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: unresolved symbol
On Mon, Dec 31, 2001 at 02:47:28PM -0800, Bob Piatek wrote:
> Correct me if I'm wrong, but it looks like the problem is caused by
the
> kernel not exporting the symbols that are needed by the module and not
> in the actual module itself. Is it that I built the kernel wrong
> somehow, or maybe the libraries in 'simple-ramdisk' image aren't
> sufficient, or is it something else?
Well, the kernel knows about its symbols at compile time, based on stuff
from the modutils program. So, if you have a bad/missing genksyms
program, you won't get any symbols.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-01-01 0:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 1:02 unresolved symbol Bob Piatek
2001-12-31 15:32 ` Tom Rini
2001-12-31 22:47 ` Bob Piatek
2001-12-31 23:01 ` Tom Rini
2002-01-01 0:47 ` Bob Piatek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-24 7:11 zhonglei
2005-08-24 7:07 zhonglei
2005-08-24 8:59 ` Alex Zeffertt
[not found] <B25E2E5A003CD311B61E00902778AF2A034573AB@SERVER1>
2001-09-24 16:31 ` Shoudong XU
2001-09-24 15:24 Shoudong XU
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='000601c1925d$e4bcd940$a2341204@P4' \
--to=bobtek@fishcamp.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).