Re: Unresolved symbols 2.4.18-pre9-mjc2

From: Adam Schrotenboer (adam@tabris.net)
Date: Thu Mar 07 2002 - 11:14:07 EST

Next message: Larry McVoy: "Re: Why not an arch mirror for the kernel?"
Previous message: Matt: "sunhme.o+SMP, the fourth QFE port interrupt mystery"
In reply to: Adam Schrotenboer: "Unresolved symbols 2.4.18-pre9-mjc2"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Well, found the solution (in the archives) is to add
EXPORT_SYMBOL(blkdev_varyio) to ksyms.

--
tabris
On Thursday 07 March 2002 02:22, Adam Schrotenboer wrote:
> Been a bit busy lately, but after the power went off last night, I
> decided to finish my compile of the latest (afaict) mjc kernel.
>
> Already commented out a function (it was several days ago, I can't
> remember it.) that was obsoleted by the radix tree patch. Now, I come
> up w/ this error in modules_install .
>
> Ideas?
>
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-pre9-mjc2/kernel/drivers/scsi/sd_mod.o
> depmod: 	blkdev_varyio
>
> TIA
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Next message: Larry McVoy: "Re: Why not an arch mirror for the kernel?"
Previous message: Matt: "sunhme.o+SMP, the fourth QFE port interrupt mystery"
In reply to: Adam Schrotenboer: "Unresolved symbols 2.4.18-pre9-mjc2"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Mar 07 2002 - 21:01:04 EST