From: Keith Owens <kaos@ocs.com.au>
To: Chuck Harding <charding@llnl.gov>
Cc: Linux Kernel Discussion List <linux-kernel@vger.kernel.org>
Subject: Re: Subject: Unresolved symbols from 'make modules_install'
Date: Wed, 04 Jun 2003 15:24:01 +1000 [thread overview]
Message-ID: <1982.1054704241@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 03 Jun 2003 10:27:05 MST." <Pine.LNX.4.55.0306031017070.9083@ghostwheel.llnl.gov>
On Tue, 3 Jun 2003 10:27:05 -0700 (PDT),
Chuck Harding <charding@llnl.gov> wrote:
>with no errors, when I run the 'make modules_install' I get a bunch
>of occurrances of unresolved symbol errors from 'depmod -ae -F System.map 2.x.x'
>most of which are for what appear to be core functions that the
>modules would need (output is attached
You did not include any output from make modules_install.
>as is my .config
.config is from a 2.5 kernel, not 2.4.
next prev parent reply other threads:[~2003-06-04 5:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 17:27 Subject: Unresolved symbols from 'make modules_install' Chuck Harding
2003-06-04 5:24 ` Keith Owens [this message]
2003-06-04 15:03 ` Chuck Harding
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=1982.1054704241@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=charding@llnl.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 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).