From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Florian Larysch <fl@n621.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/bash: fix build with host GCC 15
Date: Wed, 7 May 2025 22:28:29 +0200 [thread overview]
Message-ID: <20250507222829.2fee8926@windsurf> (raw)
In-Reply-To: <20250507185930.6cosxy42ale5wqw2@n621.de>
Hello Florian,
On Wed, 7 May 2025 20:59:30 +0200
Florian Larysch <fl@n621.de> wrote:
> Note that this is also going to cause issues for the target build once
> toolchains start picking up GCC 15, but since this also requires
> touching the toolchain infrastructure to make Buildroot aware of GCC 15
> and I'm not too familiar with that I wanted to keep the patch for the
> acute issue separate.
I already posted patches to add GCC 15.x support in Buildroot:
https://patchwork.ozlabs.org/project/buildroot/list/?series=454269
however, we haven't merged this series for now precisely because we
know there are a LOT of packages that are failing to build with GCC
15.x. We expect to merge the GCC 15.x support after Buildroot 2025.05
has been released.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-05-07 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 18:53 [Buildroot] [PATCH 1/1] package/bash: fix build with host GCC 15 Florian Larysch
2025-05-07 18:59 ` Florian Larysch
2025-05-07 20:28 ` Thomas Petazzoni via buildroot [this message]
2025-05-07 20:45 ` Florian Larysch
2025-05-08 17:11 ` Julien Olivain
2025-05-16 11:06 ` 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=20250507222829.2fee8926@windsurf \
--to=buildroot@buildroot.org \
--cc=fl@n621.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox