From: Ethan Blanton <eblanton@cs.ohiou.edu>
To: Armando Di Cianno <diciaa@rpi.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.4.7preX - unresolved symbols/compilation problem
Date: Tue, 17 Jul 2001 13:15:57 -0400 [thread overview]
Message-ID: <20010717131557.H22214@localhost.localdomain> (raw)
In-Reply-To: <20010717091235.G29799@garmonbozia.productivitynet.com>; from diciaa@rpi.edu on Tue, Jul 17, 2001 at 09:12:35AM -0400
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
Armando Di Cianno spake unto us the following wisdom:
> I started with an ultra-basic install of YellowDog 2.0 on my TiBook (I
> wanted the glibc 2.2, and I like compiling everything else by hand).
> However, now that everything is up to par, I tried compiling both the benh
> and bk 2.4.7preX trees, and while they compile, upon reboot, all modules
> complain about unresolved symbols, even though cat'ng System.map reveals
> that those symbols are there (stuff like printk!!!).
I had this problem, too, when I just updated and then 'make oldconfig;
make dep vmlinux...'d it. However, a 'make distclean' and then
reconfiguring fixed it for me.
Ethan
--
If I've told you once, I've told you once
And once is all that you needed.
-- The Refreshments, "Carefree"
[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]
next prev parent reply other threads:[~2001-07-17 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 13:12 2.4.7preX - unresolved symbols/compilation problem Armando Di Cianno
2001-07-17 17:15 ` Ethan Blanton [this message]
2001-07-17 17:17 ` Tom Rini
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=20010717131557.H22214@localhost.localdomain \
--to=eblanton@cs.ohiou.edu \
--cc=diciaa@rpi.edu \
--cc=linuxppc-dev@lists.linuxppc.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).