From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: "Joseph Zikusooka (ZIK)" <josephzik@gmail.com>
Cc: buildroot@buildroot.org, "Joseph Zikusooka (ZIK)" <zik@jambula.net>
Subject: Re: [Buildroot] [PATCH v2] package/m4: fix build failure with gcc 15
Date: Sat, 3 May 2025 14:41:31 +0200 [thread overview]
Message-ID: <20250503144131.0b1fa2df@booty> (raw)
In-Reply-To: <20250503114339.13240-1-zik@jambula.net>
Hello Joseph,
thanks for your patch!
On Sat, 3 May 2025 14:43:39 +0300
"Joseph Zikusooka (ZIK)" <josephzik@gmail.com> wrote:
> This is a temporary workaround to address build issues with host-m4 when using GCC 15, as encountered on
> the recently released Fedora 42. The issue stems from stricter compiler behavior introduced in recent
> versions of GCC.
>
> A proper fix has already been committed upstream and will be included in the next release of GNU m4:
> https://git.savannah.gnu.org/cgit/m4.git/commit/?h=branch-1.4&id=a22c9802dd7e724eaefb21dc21d84ac2d3a49c89
>
> Until that version is available in buildroot, this patch ensures continued compatibility and successful
> builds.
>
> More context:
> https://lists.buildroot.org/pipermail/buildroot/2025-April/776922.html
>
> Signed-off-by: Joseph Zikusooka (ZIK) <zik@jambula.net>
The patch diff is identical to v1, thus you could have copied the
Tested-by tags you got.
Anyway:
[Tested v1, but v2 has the same diff]
Tested-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Also, adding a changelog after the '---' line is useful.
E.g.:
Changes in v2:
- reworded commit message (no diff changes)
Luca
--
Luca Ceresoli, 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-05-03 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-03 11:43 [Buildroot] [PATCH v2] package/m4: fix build failure with gcc 15 Joseph Zikusooka (ZIK)
2025-05-03 12:41 ` Luca Ceresoli via buildroot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-03 13:52 [Buildroot] (no subject) Joseph Zikusooka (ZIK)
2025-05-03 13:52 ` [Buildroot] [PATCH v2] package/m4: fix build failure with gcc 15 Joseph Zikusooka (ZIK)
2025-05-04 17:45 ` Julien Olivain
2025-05-04 18:57 ` Joseph Zikusooka
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=20250503144131.0b1fa2df@booty \
--to=buildroot@buildroot.org \
--cc=josephzik@gmail.com \
--cc=luca.ceresoli@bootlin.com \
--cc=zik@jambula.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