From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/pax-utils: needs kernel headers >= 3.5
Date: Sat, 27 Feb 2016 20:56:35 +0100 [thread overview]
Message-ID: <1456602995-22546-1-git-send-email-romain.naour@gmail.com> (raw)
pax-utils require a toolchain with kernel headers >= 3.5 to provide
PR_SET_NO_NEW_PRIVS.
Fixes:
http://autobuild.buildroot.net/results/a9e/a9e0287e67c03e5e385bf54578aa6c5c85206ec2
Signed-off-by: Romain Naour <romain.naour@gmail.com>
---
package/pax-utils/Config.in | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/package/pax-utils/Config.in b/package/pax-utils/Config.in
index 58100e4..e61d9b3 100644
--- a/package/pax-utils/Config.in
+++ b/package/pax-utils/Config.in
@@ -1,7 +1,11 @@
config BR2_PACKAGE_PAX_UTILS
bool "pax-utils"
+ depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_5 # needs PR_SET_NO_NEW_PRIVS
help
ELF related utils for ELF 32/64 binaries that can check files
for security relevant properties.
http://www.gentoo.org/proj/en/hardened/pax-utils.xml
+
+comment "pax-utils needs a toolchain w/ headers >= 3.5"
+ depends on !BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_5
--
2.5.0
next reply other threads:[~2016-02-27 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 19:56 Romain Naour [this message]
2016-02-27 22:22 ` [Buildroot] [PATCH] package/pax-utils: needs kernel headers >= 3.5 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=1456602995-22546-1-git-send-email-romain.naour@gmail.com \
--to=romain.naour@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