From: "J.A. Magallon" <jamagallon@able.es>
To: Daniel.A.Christian@NASA.gov
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-rc7 SMP module unresolved symbols
Date: Wed, 4 Jun 2003 10:31:50 +0200 [thread overview]
Message-ID: <20030604083150.GA2770@werewolf.able.es> (raw)
In-Reply-To: <200306031728.41982.Daniel.A.Christian@NASA.gov>; from Daniel.A.Christian@NASA.gov on Wed, Jun 04, 2003 at 02:28:41 +0200
On 06.04, Dan Christian wrote:
> I can build a 2.4.21-rc7 Athlon single processor kernel and modules
> without problem.
>
> When I enable SMP, most (but not all) modules have unresolved symbols.
> This is basic stuff like prink and kmalloc. I've tried both with and
> without symbol versioning.
>
> The build line was:
> make clean && make dep && make bzImage && make modules && make
> modules_install
>
You're missing a make install, I think ( at least this is what I do,
perhaps something is redundant:
make clean
make dep
make bzImage
make install <<<<<<<<<<<<<<<<
make modules
make modules_install
Wthout the make install yu don't have nor the new kernel nor the System.map
in /boot.
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.2 (Cooker) for i586
Linux 2.4.21-rc7-jam1 (gcc 3.3 (Mandrake Linux 9.2 3.3-1mdk))
next prev parent reply other threads:[~2003-06-04 8:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 0:28 2.4.21-rc7 SMP module unresolved symbols Dan Christian
2003-06-04 0:32 ` Marc-Christian Petersen
2003-06-04 16:00 ` Dan Christian
2003-06-04 5:30 ` Keith Owens
2003-06-04 8:31 ` J.A. Magallon [this message]
2003-06-04 9:34 ` Clemens Schwaighofer
2003-06-04 15:57 ` Dan Christian
[not found] <434747C01D5AC443809D5FC5405011314BEC@bobcat.unickz.com>
2003-06-04 18:06 ` Dan Christian
2003-06-04 19:36 ` Samuel Flory
2003-06-04 20:00 ` Richard B. Johnson
2003-06-04 21:33 ` Alan Cox
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=20030604083150.GA2770@werewolf.able.es \
--to=jamagallon@able.es \
--cc=Daniel.A.Christian@NASA.gov \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.