From: "Clément Leger" <cleger@kalray.eu>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] toolchain: add BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_1
Date: Thu, 4 Apr 2019 09:01:11 +0200 (CEST) [thread overview]
Message-ID: <1905283465.159802.1554361271608.JavaMail.zimbra@kalray.eu> (raw)
Signed-off-by: Clement Leger <clement.leger@kalray.eu>
---
toolchain/Config.in | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/toolchain/Config.in b/toolchain/Config.in
index 552220123f..8c5a4fb88e 100644
--- a/toolchain/Config.in
+++ b/toolchain/Config.in
@@ -404,10 +404,15 @@ config BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_0
bool
select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_20
+config BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_1
+ bool
+ select BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_0
+
# This order guarantees that the highest version is set, as kconfig
# stops affecting a value on the first matching default.
config BR2_TOOLCHAIN_HEADERS_AT_LEAST
string
+ default "5.1" if BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_1
default "5.0" if BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_0
default "4.20" if BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_20
default "4.19" if BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_19
--
2.15.0.276.g89ea799
next reply other threads:[~2019-04-04 7:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 7:01 Clément Leger [this message]
2019-04-04 7:01 ` [Buildroot] [PATCH 2/3] toolchain/toolchain-external-custom: support Linux 5.1 Clément Leger
2019-04-04 7:03 ` [Buildroot] [PATCH 3/3] package/linux-headers: add support for Linux 5.1 kernel headers Clément Leger
2019-04-07 7:13 ` Peter Korsgaard
2019-04-08 7:18 ` Clément Leger
2019-04-08 7:47 ` Peter Korsgaard
2019-04-08 8:06 ` Clément Leger
2019-04-08 10:47 ` Peter Korsgaard
2019-04-07 7:13 ` [Buildroot] [PATCH 2/3] toolchain/toolchain-external-custom: support Linux 5.1 Peter Korsgaard
2019-04-07 7:12 ` [Buildroot] [PATCH 1/3] toolchain: add BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_1 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=1905283465.159802.1554361271608.JavaMail.zimbra@kalray.eu \
--to=cleger@kalray.eu \
--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