From: dmeyer@dmeyer.net
To: linux-kernel@vger.kernel.org
Subject: Re: unresolved symbol in 2.4.1 depmod.
Date: Tue, 30 Jan 2001 18:27:40 -0500 [thread overview]
Message-ID: <20010130182740.A10610@jhereg.dmeyer.net> (raw)
In-Reply-To: <Pine.SOL.4.20.0101301409420.20128-100000@garnet.tc.umn.edu>
In-Reply-To: <4924.980894540@ocs3.ocs-net>
In article <4924.980894540@ocs3.ocs-net> you write:
> On Tue, 30 Jan 2001 14:15:20 -0600 (CST),
> Jason Michaelson <micha044@tc.umn.edu> wrote:
> >Greetings. I've just procured myself a copy of 2.4.1, and tried to build
> >it. At the tail end of a make modules_install, the following error occurs:
> >
> >depmod: *** Unresolved symbols in /lib/modules/2.4.1/kernel/drivers/md/md.o
> >depmod: name_to_kdev_t
>
> name_to_kdev_t is defined in init/main.c. It is not exported so it
> cannot be called from modules. name_to_kdev_t *cannot* be exported
> because it is defined as __init, the code has gone by the time the
> module is loaded. Ask the md maintainer for a fix.
How did this used to work, then? The call to name_to_kdev_t has been
in the md code since (according to the code comments) May, 2000; the
module worked fine as of 2.4.1-pre10, which is the last version I used.
--
Dave Meyer
dmeyer@dmeyer.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-30 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 20:15 unresolved symbol in 2.4.1 depmod Jason Michaelson
2001-01-30 22:42 ` Keith Owens
2001-01-30 23:27 ` dmeyer [this message]
2001-01-31 2:34 ` Keith Owens
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=20010130182740.A10610@jhereg.dmeyer.net \
--to=dmeyer@dmeyer.net \
--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