From: Andrea Arcangeli <andrea@suse.de>
To: Christian Guggenberger
<christian.guggenberger@physik.uni-regensburg.de>
Cc: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-pre10-aa1: unresolved symbol in xfs.o
Date: Tue, 15 Oct 2002 19:16:15 +0200 [thread overview]
Message-ID: <20021015171615.GF2546@dualathlon.random> (raw)
In-Reply-To: <20021015184148.A5026@pc9391.uni-regensburg.de>
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
next prev parent reply other threads:[~2002-10-15 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 15:25 Christian Guggenberger
2002-10-15 16:19 ` Andrea Arcangeli
2002-10-15 16:41 ` Christian Guggenberger
2002-10-15 17:16 ` Andrea Arcangeli [this message]
2002-10-15 18:12 ` Christoph Hellwig
2002-10-15 21:36 ` Andrea Arcangeli
2002-10-15 21:35 ` Andi Kleen
2002-10-16 10:35 ` 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=20021015171615.GF2546@dualathlon.random \
--to=andrea@suse.de \
--cc=christian.guggenberger@physik.uni-regensburg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
/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
all inboxes | Powered by JetHome®