From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH] package/botan: needs thread support
Date: Mon, 19 Aug 2024 11:44:56 +0200 [thread overview]
Message-ID: <ZsMUGMbnR2mwtwj6@waldemar-brodkorb.de> (raw)
Botan commit 313e439c786d68bcf374b2cb0edfe3ffd891db94 added a
dependency to pthread.h. Add a dependency to thread support.
Fixes:
- http://autobuild.buildroot.org/results/205/205d7505803990508bbd545393902789063ababd
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
package/botan/Config.in | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/package/botan/Config.in b/package/botan/Config.in
index c74128bb9d..c61b368801 100644
--- a/package/botan/Config.in
+++ b/package/botan/Config.in
@@ -16,6 +16,7 @@ config BR2_PACKAGE_BOTAN
depends on BR2_INSTALL_LIBSTDCPP
depends on BR2_TOOLCHAIN_GCC_AT_LEAST_10 # C++20
depends on BR2_PACKAGE_BOTAN_ARCH_SUPPORTS
+ depends on BR2_TOOLCHAIN_HAS_THREADS
select BR2_PACKAGE_BOOST_FILESYSTEM if BR2_PACKAGE_BOOST && BR2_TOOLCHAIN_SUPPORTS_ALWAYS_LOCKFREE_ATOMIC_INTS
select BR2_PACKAGE_BOOST_SYSTEM if BR2_PACKAGE_BOOST && BR2_TOOLCHAIN_SUPPORTS_ALWAYS_LOCKFREE_ATOMIC_INTS
help
@@ -23,7 +24,8 @@ config BR2_PACKAGE_BOTAN
http://botan.randombit.net
-comment "botan needs a toolchain w/ C++, gcc >= 10"
+comment "botan needs a toolchain w/ threads, C++, gcc >= 10"
depends on !BR2_INSTALL_LIBSTDCPP \
- || !BR2_TOOLCHAIN_GCC_AT_LEAST_10
+ || !BR2_TOOLCHAIN_GCC_AT_LEAST_10 \
+ || !BR2_TOOLCHAIN_HAS_THREADS
depends on BR2_PACKAGE_BOTAN_ARCH_SUPPORTS
--
2.39.2
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-08-19 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 9:44 Waldemar Brodkorb [this message]
2024-08-19 10:48 ` [Buildroot] [PATCH] package/botan: needs thread support Thomas Petazzoni via buildroot
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=ZsMUGMbnR2mwtwj6@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@buildroot.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.