From: Ilya Averyanov <averyanovin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] exempi: add dependency on threads
Date: Sun, 6 Jan 2019 01:47:27 +0300 [thread overview]
Message-ID: <20190105224727.5357-1-averyanovin@gmail.com> (raw)
Signed-off-by: Ilya Averyanov <averyanovin@gmail.com>
---
package/exempi/Config.in | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/package/exempi/Config.in b/package/exempi/Config.in
index b3ec2c513d..0fa4b473bc 100644
--- a/package/exempi/Config.in
+++ b/package/exempi/Config.in
@@ -2,6 +2,7 @@ config BR2_PACKAGE_EXEMPI
bool "exempi"
depends on !BR2_STATIC_LIBS # dlfcn.h
depends on BR2_INSTALL_LIBSTDCPP
+ depends on BR2_TOOLCHAIN_HAS_THREADS
select BR2_PACKAGE_EXPAT
select BR2_PACKAGE_ZLIB
help
@@ -10,5 +11,5 @@ config BR2_PACKAGE_EXEMPI
http://libopenraw.freedesktop.org/wiki/Exempi
-comment "exempi needs a toolchain w/ C++, dynamic library"
- depends on BR2_STATIC_LIBS || BR2_INSTALL_LIBSTDCPP
+comment "exempi needs a toolchain w/ C++, dynamic library, threads
+ depends on BR2_STATIC_LIBS || !BR2_INSTALL_LIBSTDCPP || !BR2_TOOLCHAIN_HAS_THREADS
--
2.19.1
next reply other threads:[~2019-01-05 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 22:47 Ilya Averyanov [this message]
2019-01-06 20:23 ` [Buildroot] [PATCH 1/1] exempi: add dependency on 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=20190105224727.5357-1-averyanovin@gmail.com \
--to=averyanovin@gmail.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