From: ulf at uclibc.org <ulf@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package: nfs-utils portmap
Date: Tue, 30 Oct 2007 14:15:46 -0700 (PDT) [thread overview]
Message-ID: <20071030211546.2F1ABA6129@busybox.net> (raw)
Author: ulf
Date: 2007-10-30 14:15:46 -0700 (Tue, 30 Oct 2007)
New Revision: 20336
Log:
Hint at 'enable RPC' requirement for nfs-utils and portmap
Modified:
trunk/buildroot/package/nfs-utils/Config.in
trunk/buildroot/package/portmap/Config.in
Changeset:
Modified: trunk/buildroot/package/nfs-utils/Config.in
===================================================================
--- trunk/buildroot/package/nfs-utils/Config.in 2007-10-30 20:14:12 UTC (rev 20335)
+++ trunk/buildroot/package/nfs-utils/Config.in 2007-10-30 21:15:46 UTC (rev 20336)
@@ -1,5 +1,6 @@
config BR2_PACKAGE_NFS_UTILS
bool "nfs-utils"
+ depends on BR2_INET_RPC
default n
help
The NFS Linux kernel server.
@@ -8,6 +9,9 @@
http://sourceforge.net/projects/nfs
+comment "nfs-utils requires a toolchain with 'Enable RPC' selected"
+ depends on !BR2_INET_RPC
+
menu "NFS utilities selection"
depends BR2_PACKAGE_NFS_UTILS
Modified: trunk/buildroot/package/portmap/Config.in
===================================================================
--- trunk/buildroot/package/portmap/Config.in 2007-10-30 20:14:12 UTC (rev 20335)
+++ trunk/buildroot/package/portmap/Config.in 2007-10-30 21:15:46 UTC (rev 20336)
@@ -1,7 +1,11 @@
config BR2_PACKAGE_PORTMAP
bool "portmap"
default n
+ depends on BR2_INET_RPC
help
The standard portmapper for RPC services.
ftp://ftp.porcupine.org/pub/security/index.html
+
+comment "portmap requires a toolchain with 'Enable RPC' selected"
+ depends on !BR2_INET_RPC
reply other threads:[~2007-10-30 21:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20071030211546.2F1ABA6129@busybox.net \
--to=ulf@uclibc.org \
--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