From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ifupdown: wordexp is enabled in uClibc now
Date: Sun, 30 Apr 2017 10:41:20 +0200 [thread overview]
Message-ID: <20170430084120.GA17431@waldemar-brodkorb.de> (raw)
Package can now be used for uClibc toolchains.
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
package/ifupdown/Config.in | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/package/ifupdown/Config.in b/package/ifupdown/Config.in
index e683201..ccacd0f 100644
--- a/package/ifupdown/Config.in
+++ b/package/ifupdown/Config.in
@@ -2,8 +2,6 @@ config BR2_PACKAGE_IFUPDOWN
bool "ifupdown"
depends on BR2_USE_MMU # fork()
depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_0 # iproute2
- # Default/our uclibc lacks wordexp()
- depends on !BR2_TOOLCHAIN_USES_UCLIBC
depends on BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
# runtime for ip binary
select BR2_PACKAGE_IPROUTE2 if !BR2_PACKAGE_BUSYBOX
@@ -14,8 +12,7 @@ config BR2_PACKAGE_IFUPDOWN
https://tracker.debian.org/pkg/ifupdown
-comment "ifupdown needs a glibc or musl toolchain w/ headers >= 3.0"
+comment "ifupdown needs a toolchain w/ headers >= 3.0"
depends on BR2_USE_MMU
- depends on BR2_TOOLCHAIN_USES_UCLIBC || \
- !BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_0
+ depends on !BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_0
depends on BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
--
2.1.4
next reply other threads:[~2017-04-30 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 8:41 Waldemar Brodkorb [this message]
2017-05-01 7:22 ` [Buildroot] [PATCH] ifupdown: wordexp is enabled in uClibc now Thomas Petazzoni
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=20170430084120.GA17431@waldemar-brodkorb.de \
--to=wbx@openadk.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