| To: | Andrea Arcangeli <andrea@xxxxxxx> |
|---|---|
| Subject: | Re: 2.4.20-pre10-aa1: unresolved symbol in xfs.o |
| From: | Christian Guggenberger <christian.guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx> |
| Date: | Tue, 15 Oct 2002 18:41:48 +0200 |
| Cc: | linux-xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| In-reply-to: | <20021015161908.GC2546@xxxxxxxxxxxxxxxxx>; from andrea@xxxxxxx on Tue, Oct 15, 2002 at 18:19:08 +0200 |
| References: | <20021015172558.A3154@xxxxxxxxxxxxxxxxxxxxxxxx> <20021015161908.GC2546@xxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
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 Christian |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: re[2]: Work Items, Steve Lord |
|---|---|
| Next by Date: | Re: [2.4.18-14SGI_XFS_1.2a1] acl problems (was: root xfs filesystem executable bits bug comeback?), Eric Sandeen |
| Previous by Thread: | Re: 2.4.20-pre10-aa1: unresolved symbol in xfs.o, Andrea Arcangeli |
| Next by Thread: | Re: 2.4.20-pre10-aa1: unresolved symbol in xfs.o, Andrea Arcangeli |
| Indexes: | [Date] [Thread] [Top] [All Lists] |