From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] atest: wordexp is enabled in uClibc now
Date: Sun, 30 Apr 2017 10:40:43 +0200 [thread overview]
Message-ID: <20170430084043.GA17408@waldemar-brodkorb.de> (raw)
Package can now be used for uClibc toolchains.
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
package/atest/Config.in | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/package/atest/Config.in b/package/atest/Config.in
index 1b357bb..9a2e342 100644
--- a/package/atest/Config.in
+++ b/package/atest/Config.in
@@ -1,6 +1,5 @@
config BR2_PACKAGE_ATEST
bool "atest"
- depends on !BR2_TOOLCHAIN_USES_UCLIBC # uclibc lacks wordexp
depends on BR2_TOOLCHAIN_HAS_THREADS # alsa-lib
depends on !BR2_bfin # libev
select BR2_PACKAGE_ALSA_LIB
@@ -11,6 +10,6 @@ config BR2_PACKAGE_ATEST
https://github.com/amouiche/atest
-comment "atest needs a glibc or musl toolchain w/ threads"
+comment "atest needs a toolchain w/ threads"
depends on !BR2_bfin
- depends on BR2_TOOLCHAIN_USES_UCLIBC || !BR2_TOOLCHAIN_HAS_THREADS
+ depends on !BR2_TOOLCHAIN_HAS_THREADS
--
2.1.4
next reply other threads:[~2017-04-30 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 8:40 Waldemar Brodkorb [this message]
2017-05-01 7:22 ` [Buildroot] [PATCH] atest: 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=20170430084043.GA17408@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