From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] Anyone know why Buildroot complains about uClibc RPC for NFS support?
Date: Wed, 7 May 2008 12:09:54 +1000 [thread overview]
Message-ID: <20080507020954.GA28208@cloud.net.au> (raw)
In-Reply-To: <326f33790805061757l56e09784x5021e51f919479b5@mail.gmail.com>
On Tue, May 06, 2008 at 05:57:45PM -0700, Arun Reddy wrote:
> #error "*You* *need to build uClibc with UCLIBC_HAS_RPC* for NFS support."
>
> http://img254.imageshack.us/img254/8638/rpcproblemka7.jpg
>
> I am not understanding this error, because I never wanted support for NFS in
> the first place. (I just want to build something that will run in QEMU).
> Does anyone know why I get this error and why it complains about NFS support
> even though I disabled it in the kernel?
The kernel doesn't use uClibc, and disabling NFS in the kernel isn't
enough. Maybe you have the NFS utilities package enabled, and/or NFS mount
support in busybox?
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2008-05-07 2:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 0:57 [Buildroot] Anyone know why Buildroot complains about uClibc RPC for NFS support? Arun Reddy
2008-05-07 2:09 ` Hamish Moffatt [this message]
2008-05-07 7:42 ` Arun Reddy
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=20080507020954.GA28208@cloud.net.au \
--to=hamish@cloud.net.au \
--cc=buildroot@busybox.net \
/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