From: Adam Duskett <aduskett@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] libsepol: require threads
Date: Wed, 25 Oct 2017 09:12:00 -0400 [thread overview]
Message-ID: <20171025131200.18412-1-aduskett@gmail.com> (raw)
libsepol 2.7 now uses pthreads.h
Signed-off-by: Adam Duskett <aduskett@gmail.com>
---
Changes v1 -> v2:
- Added thread dependency to semodule-utils (Arnout)
Changes v2 -> v3:
- Added explinations for dependencies (Matt Webber)
package/libsepol/Config.in | 1 +
package/semodule-utils/Config.in | 4 ++++
2 files changed, 5 insertions(+)
diff --git a/package/libsepol/Config.in b/package/libsepol/Config.in
index f92af52072..f17eb47448 100644
--- a/package/libsepol/Config.in
+++ b/package/libsepol/Config.in
@@ -1,5 +1,6 @@
config BR2_PACKAGE_LIBSEPOL
bool "libsepol"
+ depends on BR2_TOOLCHAIN_HAS_THREADS # pthread
help
Libsepol is the binary policy manipulation library. It doesn't
depend upon or use any of the other SELinux components.
diff --git a/package/semodule-utils/Config.in b/package/semodule-utils/Config.in
index d9cb928c4c..38e043dc2c 100644
--- a/package/semodule-utils/Config.in
+++ b/package/semodule-utils/Config.in
@@ -1,5 +1,6 @@
config BR2_PACKAGE_SEMODULE_UTILS
bool "semodule-utils"
+ depends on BR2_TOOLCHAIN_HAS_THREADS # libsepol
select BR2_PACKAGE_LIBSEPOL
help
semodule-utils is a package that contains tools for handling
@@ -13,3 +14,6 @@ config BR2_PACKAGE_SEMODULE_UTILS
* semodule_package - Create a SELinux policy module package.
https://github.com/SELinuxProject/selinux/wiki/Releases
+
+comment "semodule-utils needs a toolchain w/ threads"
+ depends on !BR2_TOOLCHAIN_HAS_THREADS
--
2.13.6
next reply other threads:[~2017-10-25 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 13:12 Adam Duskett [this message]
2017-10-25 13:21 ` [Buildroot] [PATCH v3 1/1] libsepol: require threads Matthew Weber
2017-10-27 9:20 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2017-10-25 14:14 Adam Duskett
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=20171025131200.18412-1-aduskett@gmail.com \
--to=aduskett@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