From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] Config.in: introduce BR2_HOST_GCC_AT_LEAST_{12..15}
Date: Mon, 21 Apr 2025 23:51:13 +0200 [thread overview]
Message-ID: <20250421235113.4052b53e@windsurf> (raw)
In-Reply-To: <20250320223549.138974-1-ju.o@free.fr>
On Thu, 20 Mar 2025 23:35:49 +0100
Julien Olivain <ju.o@free.fr> wrote:
> Fedora 42 is planned to be released on 2025-04-22 [1].
> It is also planned to include the upcoming gcc 15 release.
> Gcc 15 is changing the default C language from -std=gnu17
> to -std=gnu23 [2].
>
> This change is expected to possibly introduce build failures [3].
> In order to be prepared to fix those, this commit introduces the
> BR2_HOST_GCC_AT_LEAST_{12..15} symbols.
>
> [1] https://fedorapeople.org/groups/schedule/f-42/f-42-key-tasks.html
> [2] https://gcc.gnu.org/gcc-15/changes.html#c
> [3] https://savannah.gnu.org/support/?111150
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> Config.in | 20 ++++++++++++++++++++
> Makefile | 2 +-
> 2 files changed, 21 insertions(+), 1 deletion(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-04-21 21:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 22:35 [Buildroot] [PATCH 1/1] Config.in: introduce BR2_HOST_GCC_AT_LEAST_{12..15} Julien Olivain
2025-04-21 21:51 ` Thomas Petazzoni via buildroot [this message]
2025-05-16 11:03 ` Arnout Vandecappelle 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=20250421235113.4052b53e@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--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.