From: Alan Cox <alan@redhat.com>
To: elenstev@mesatop.com (Steven Cole)
Cc: alan@redhat.com (Alan Cox), linux-kernel@vger.kernel.org (Linux Kernel)
Subject: Re: Linux 2.4.20-pre2-ac1
Date: Wed, 14 Aug 2002 20:07:19 -0400 (EDT) [thread overview]
Message-ID: <200208150007.g7F07JU05425@devserv.devel.redhat.com> (raw)
In-Reply-To: <1029346932.2045.128.camel@spc9.esa.lanl.gov> from "Steven Cole" at Aug 14, 2002 11:42:11 AM
> fs/fs.o: In function `nfsd':
> fs/fs.o(.text+0x43fb1): undefined reference to `exp_readunlock'
> fs/fs.o: In function `sys_nfsservctl':
> fs/fs.o(.text+0x445e8): undefined reference to `exp_readunlock'
> fs/fs.o(.text+0x44692): undefined reference to `exp_readunlock'
> fs/fs.o(.data+0x261c): undefined reference to `exp_readunlock'
> make: *** [vmlinux] Error 1
>
> Unsetting CONFIG_NFSD allowed me to build 2.4.20-pre2-ac1.
Interesting. The NFS merge was nontrivial so thats not a huge suprise.
What is however is that it apparently built for me
next prev parent reply other threads:[~2002-08-15 0:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-14 16:34 Alan Cox
2002-08-14 16:44 ` Christoph Hellwig
2002-08-14 16:46 ` Alan Cox
2002-08-14 17:42 ` Steven Cole
2002-08-14 20:29 ` Greg Louis
2002-08-14 21:06 ` Steven Cole
2002-08-15 0:07 ` Alan Cox [this message]
2002-08-14 17:54 ` Javier Marcet
2002-08-14 18:03 ` Christoph Hellwig
2002-08-14 19:44 ` Unresolved symbols in nfsd in 2.4.20-pre2-ac1 Samuel Flory
2002-08-14 22:11 ` Linux 2.4.20-pre2-ac1 Adrian Bunk
2002-08-14 22:47 ` Adrian Bunk
2002-08-14 23:56 ` Chad Young
2002-08-15 1:03 ` Eyal Lebedinsky
2002-08-15 1:14 ` Alan Cox
2002-08-15 2:30 ` Kai Germaschewski
2002-08-15 10:52 ` Alan Cox
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=200208150007.g7F07JU05425@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.org \
/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®