All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 for-next 1/5] arch: add BR2_ARCH_NEEDS_GCC_AT_LEAST_8
Date: Tue, 29 May 2018 23:52:53 +0200	[thread overview]
Message-ID: <20180529215257.17686-1-romain.naour@gmail.com> (raw)

This new symbol will be used by architectures introduced with gcc 8 and
by external toolchains based on gcc 8.

[1] https://gcc.gnu.org/gcc-8/changes.html

Signed-off-by: Romain Naour <romain.naour@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
 arch/Config.in | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/arch/Config.in b/arch/Config.in
index a66ea0d03b..a16012bdfd 100644
--- a/arch/Config.in
+++ b/arch/Config.in
@@ -282,6 +282,10 @@ config BR2_ARCH_NEEDS_GCC_AT_LEAST_7
 	bool
 	select BR2_ARCH_NEEDS_GCC_AT_LEAST_6
 
+config BR2_ARCH_NEEDS_GCC_AT_LEAST_8
+	bool
+	select BR2_ARCH_NEEDS_GCC_AT_LEAST_7
+
 # The following string values are defined by the individual
 # Config.in.$ARCH files
 config BR2_ARCH
-- 
2.14.3

             reply	other threads:[~2018-05-29 21:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29 21:52 Romain Naour [this message]
2018-05-29 21:52 ` [Buildroot] [PATCH v3 for-next 2/5] toolchain: add gcc 8 entry Romain Naour
2018-05-29 21:52 ` [Buildroot] [PATCH v3 for-next 3/5] package/gcc: add support for gcc 8.1.0 Romain Naour
2018-05-29 21:52 ` [Buildroot] [PATCH v3 for-next 4/5] toolchain-external: add gcc 8 entry Romain Naour
2018-05-29 21:52 ` [Buildroot] [PATCH v3 for-next 5/5] package/gcc: switch to gcc 6.x as the default Romain Naour
2018-05-30 20:26 ` [Buildroot] [PATCH v3 for-next 1/5] arch: add BR2_ARCH_NEEDS_GCC_AT_LEAST_8 Thomas Petazzoni

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=20180529215257.17686-1-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 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.