* unresolved symbol in 2.4.1 depmod.
@ 2001-01-30 20:15 Jason Michaelson
2001-01-30 22:42 ` Keith Owens
0 siblings, 1 reply; 4+ messages in thread
From: Jason Michaelson @ 2001-01-30 20:15 UTC (permalink / raw)
To: linux-kernel
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
My first assumption was that this occurred because I'm running 2.2.15 with
a collection of patches. Except I've never seen this happen before with
upgrades.
Thanks,
jdm
--------
Jason D. Michaelson | Debian GNU/ o http://www.debian.org
micha044@tc.umn.edu | __
ares0@geocities.com | / / __ _ _ _ _ __ __
Jason.Michaelson@veritas.com | / /__ / / / \// //_// \ \/ /
(651)604-7263 | /____/ /_/ /_/\/ /___/ /_/\_\
http://www.tc.umn.edu/ |
~micha044 | ...because lockups are for convicts...
Converting Oxygen into Carbon Dioxide since 1977.
Getting a SCSI chain working is perfectly simple if you remember that
there must be exactly three terminations: one on one end of the cable, one
on the other end, and the goat, terminated over the SCSI chain with
a silver-handled knife whilst burning *black* candles. --- Anthony
DeBoer
-
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/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: unresolved symbol in 2.4.1 depmod.
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
0 siblings, 1 reply; 4+ messages in thread
From: Keith Owens @ 2001-01-30 22:42 UTC (permalink / raw)
To: Jason Michaelson; +Cc: linux-kernel
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.
-
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/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: unresolved symbol in 2.4.1 depmod.
2001-01-30 22:42 ` Keith Owens
@ 2001-01-30 23:27 ` dmeyer
2001-01-31 2:34 ` Keith Owens
0 siblings, 1 reply; 4+ messages in thread
From: dmeyer @ 2001-01-30 23:27 UTC (permalink / raw)
To: linux-kernel
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/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: unresolved symbol in 2.4.1 depmod.
2001-01-30 23:27 ` dmeyer
@ 2001-01-31 2:34 ` Keith Owens
0 siblings, 0 replies; 4+ messages in thread
From: Keith Owens @ 2001-01-31 2:34 UTC (permalink / raw)
To: linux-kernel
On Tue, 30 Jan 2001 18:27:40 -0500,
dmeyer@dmeyer.net wrote:
>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.
It might have worked as built in code, I would be astounded if it ever
worked as a module on a standard kernel after that code was added.
name_to_kdev_t has been defined as this since at least 2.4.0-test1.
kdev_t __init name_to_kdev_t(char *line)
You cannot export a symbol marked __init and expect it to work.
-
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/
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2001-01-31 2:34 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2001-01-31 2:34 ` Keith Owens
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox