xfs
[Top] [All Lists]

Re: 2.4.20-pre10-aa1: unresolved symbol in xfs.o

To: Christian Guggenberger <christian.guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: 2.4.20-pre10-aa1: unresolved symbol in xfs.o
From: Andrea Arcangeli <andrea@xxxxxxx>
Date: Tue, 15 Oct 2002 19:16:15 +0200
Cc: linux-xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <20021015184148.A5026@xxxxxxxxxxxxxxxxxxxxxxxx>
References: <20021015172558.A3154@xxxxxxxxxxxxxxxxxxxxxxxx> <20021015161908.GC2546@xxxxxxxxxxxxxxxxx> <20021015184148.A5026@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.27i
On Tue, Oct 15, 2002 at 06:41:48PM +0200, Christian Guggenberger wrote:
> On 15 Oct 2002 18:19:08 Andrea Arcangeli wrote:
> >On Tue, Oct 15, 2002 at 05:25:58PM +0200, Christian Guggenberger wrote:
> >> Hi Andrea,
> >>
> >> I'm trying to compile 2.4.20-pre10aa1 with xfs enabled as module.
> >> make modules_install ends up in:
> >>
> >> depmod: *** Unresolved symbols in
> >> /lib/modules/2.4.20-pre10aa1/kernel/fs/xfs/xfs.o
> >> depmod:    do_generic_file_write
> >>
> >> what to do?
> >
> >I logged it so it will be fixed. You can link it into the kernel in the
> >meantime (select Y instead of M). For some reason bleeding edge gcc from
> >CVS generates a flood of symbol errors when I run depmod before
> >rebooting, so I don't easily notice these missing exports anymore (I
> >should run depmod post reboot to notice them). thanks,
> 
> nope, static linking ends up in an error, too.
> 
> fs/fs.o: In function `xfs_write':
> fs/fs.o(.text+0xa1158): undefined reference to `do_generic_file_write'
> make: *** [vmlinux] Error 1

do_generic_file_write is missing, one patch is probably missing, I will
fix it in a few days, the last usable xfs was probably in 2.4.20pre5aa1.

Andrea


<Prev in Thread] Current Thread [Next in Thread>