From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Bernd Kuhls <bernd.kuhls@t-online.de>, buildroot@buildroot.org
Cc: Louis-Paul Cordier <lpdev@cordier.org>,
Romain Naour <romain.naour@gmail.com>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Subject: Re: [Buildroot] [PATCH 5/5] package/gcc: add support for gcc 13
Date: Tue, 16 May 2023 20:08:24 +0700 [thread overview]
Message-ID: <ZGOASHQxkCfAJIl7@debian.me> (raw)
In-Reply-To: <20230507214317.409305-5-bernd.kuhls@t-online.de>
On Sun, May 07, 2023 at 11:43:17PM +0200, Bernd Kuhls wrote:
> https://gcc.gnu.org/gcc-13/changes.html
> https://gcc.gnu.org/gcc-13/porting_to.html
>
> Patch 0002 was not ported from gcc-12 because it is included in this
> version:
> https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=ee4af2ed0b7322884ec4ff537564683c3749b813
>
Thanks for the bump! For completeness, especially for people using
Buildroot-generated toolchain as external one, you need to also allow
external GCC 13 toolchains (as separate patch of course):
---- >8 ----
From 0f12ea1536d8f1c081203bee64b9c8413cce3801 Mon Sep 17 00:00:00 2001
From: Bagas Sanjaya <bagasdotme@gmail.com>
Date: Tue, 16 May 2023 20:03:58 +0700
Subject: [PATCH] toolchain-external: Support GCC 13
Support external toolchains using GCC 13.x.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
.../toolchain-external-custom/Config.in.options | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/toolchain/toolchain-external/toolchain-external-custom/Config.in.options b/toolchain/toolchain-external/toolchain-external-custom/Config.in.options
index 0fd8841e5b..4da07566d8 100644
--- a/toolchain/toolchain-external/toolchain-external-custom/Config.in.options
+++ b/toolchain/toolchain-external/toolchain-external-custom/Config.in.options
@@ -31,6 +31,10 @@ choice
Set to the gcc version that is used by your external
toolchain.
+config BR2_TOOLCHAIN_EXTERNAL_GCC_13
+ bool "13.x"
+ select BR2_TOOLCHAIN_GCC_AT_LEAST_13
+
config BR2_TOOLCHAIN_EXTERNAL_GCC_12
bool "12.x"
select BR2_TOOLCHAIN_GCC_AT_LEAST_12
--
An old man doll... just what I always wanted! - Clara
Thanks.
--
An old man doll... just what I always wanted! - Clara
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-05-16 13:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-07 21:43 [Buildroot] [PATCH 1/5] package/intel-mediasdk: fix build with gcc-13 Bernd Kuhls
2023-05-07 21:43 ` [Buildroot] [PATCH 2/5] package/kodi: " Bernd Kuhls
2023-05-07 21:43 ` [Buildroot] [PATCH 3/5] package/kodi-inputstream-adaptive: " Bernd Kuhls
2023-07-29 21:59 ` Thomas Petazzoni via buildroot
2023-05-07 21:43 ` [Buildroot] [PATCH 4/5] package/kodi-inputstream-ffmpeg: " Bernd Kuhls
2023-07-29 21:59 ` Thomas Petazzoni via buildroot
2023-05-07 21:43 ` [Buildroot] [PATCH 5/5] package/gcc: add support for gcc 13 Bernd Kuhls
2023-05-16 13:08 ` Bagas Sanjaya [this message]
2023-05-16 13:54 ` Romain Naour
2023-05-17 6:45 ` Bagas Sanjaya
2023-07-29 21:59 ` [Buildroot] [PATCH 1/5] package/intel-mediasdk: fix build with gcc-13 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=ZGOASHQxkCfAJIl7@debian.me \
--to=bagasdotme@gmail.com \
--cc=bernd.kuhls@t-online.de \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=lpdev@cordier.org \
--cc=romain.naour@gmail.com \
--cc=thomas.de_schampheleire@nokia.com \
--cc=thomas.petazzoni@bootlin.com \
/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.