From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7682] New: Missing dependencies for NFS
Date: Sun, 30 Nov 2014 17:41:08 +0000 (UTC) [thread overview]
Message-ID: <bug-7682-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7682
Summary: Missing dependencies for NFS
Product: buildroot
Version: 2014.05
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: mfld.fr at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Selecting nfs-utils package does not automatically select the rpcbind package
(needed at runtime by rpc.statd) and does not check for RPC support in uclibc
(needed at buildtime by rpcbind).
NFS on embedded device ? Yeah, I need it on my BeagleBoneBlack for a cheap NAS
:-)
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2014-11-30 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 17:41 bugzilla at busybox.net [this message]
2015-07-30 10:13 ` [Buildroot] [Bug 7682] Missing dependencies for NFS bugzilla at busybox.net
2015-07-30 17:23 ` bugzilla at busybox.net
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=bug-7682-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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