From: Axel Lin <axel.lin@ingics.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] icu: needs threads
Date: Tue, 08 Oct 2013 09:08:21 +0800 [thread overview]
Message-ID: <1381194501.18210.0.camel@phoenix> (raw)
Fixes:
http://autobuild.buildroot.net/results/ae7/ae721db2dd4e764a2af3825c388a63cad9720ebe/
Signed-off-by: Axel Lin <axel.lin@ingics.com>
---
package/icu/Config.in | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/package/icu/Config.in b/package/icu/Config.in
index 21f5c2f..d4f4207 100644
--- a/package/icu/Config.in
+++ b/package/icu/Config.in
@@ -2,10 +2,12 @@ config BR2_PACKAGE_ICU
bool "icu"
depends on BR2_INSTALL_LIBSTDCPP
depends on BR2_USE_WCHAR
+ depends on BR2_TOOLCHAIN_HAS_THREADS
help
International Components for Unicode.
http://site.icu-project.org/
-comment "icu requires a toolchain with C++ support and WCHAR enabled"
- depends on !BR2_INSTALL_LIBSTDCPP || !BR2_USE_WCHAR
+comment "icu requires a toolchain with C++, WCHAR and threading support"
+ depends on !BR2_INSTALL_LIBSTDCPP || !BR2_USE_WCHAR || \
+ !BR2_TOOLCHAIN_HAS_THREADS
--
1.8.1.2
next reply other threads:[~2013-10-08 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 1:08 Axel Lin [this message]
2013-10-08 15:04 ` [Buildroot] [PATCH] icu: needs threads Peter Korsgaard
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=1381194501.18210.0.camel@phoenix \
--to=axel.lin@ingics.com \
--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