From: "J. Bruce Fields" <bfields@fieldses.org>
To: Andrew Zhukov <zhukov@tst.spb.su>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs-utils 1.0.8 build failure
Date: Thu, 13 Apr 2006 11:51:52 -0400 [thread overview]
Message-ID: <20060413155152.GA29358@fieldses.org> (raw)
In-Reply-To: <1144915146.32160.26.camel@localhost.localdomain>
On Thu, Apr 13, 2006 at 10:59:06AM +0300, Andrew Zhukov wrote:
> I tried to build fine "mount" for "mount -t nfs". I mean the one which
> wouldn't complain "mount is older/newer than the kernel"...
>
> First I tried to build it on x86 RedHat 9.
>
> 1. ./configure without restriction won't work... I have to use:
>
> ./configure --build=arm-linux-uclibc --enable-nfsv4=no --enable-nfsv3=no
> --enable-gss=no
>
> 2. make fails:
>
> ...
> Making all in include
> make[2]: Entering directory `/tmp/nfs-utils-1.0.8/support/include'
Note that nfs-utils doesn't provide the nfs "mount" program. You want
util-linux for that. And those mount version complaints can be safely
ignored anyway.
The kernel oopses in nfs_lookup are a separate issue, I don't know
what's causing those. So you're building in an nfs-mounted directory on
a client with a 2.6.10 kernel? Could you try a more recent kernel?
--b.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2006-04-13 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 7:59 nfs-utils 1.0.8 build failure Andrew Zhukov
2006-04-13 15:51 ` J. Bruce Fields [this message]
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=20060413155152.GA29358@fieldses.org \
--to=bfields@fieldses.org \
--cc=nfs@lists.sourceforge.net \
--cc=zhukov@tst.spb.su \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.