From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain via buildroot <buildroot@buildroot.org>
Cc: Julien Olivain <ju.o@free.fr>
Subject: Re: [Buildroot] [PATCH v2 1/1] package/berkeleydb: fix build with host gcc-15.x
Date: Mon, 28 Jul 2025 22:57:54 +0200 [thread overview]
Message-ID: <20250728225754.108b36eb@windsurf> (raw)
In-Reply-To: <20250724202406.958337-1-ju.o@free.fr>
On Thu, 24 Jul 2025 22:24:06 +0200
Julien Olivain via buildroot <buildroot@buildroot.org> wrote:
> Commit [1] fixed berkeleydb target build with gcc-15.x.
> The host variant package also fails when building with host gcc-15.x.
>
> This commit fixes the issue by replicating the same fix for the package
> host variant.
>
> Fixes:
> https://autobuild.buildroot.org/results/a8051600ab95a63c852960f8dace757b16c665f0/
>
> [1] https://gitlab.com/buildroot.org/buildroot/-/commit/c1d422edde19d07d6406705b1a4b059125dba689
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
Reviewed-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
The one thing I dislike though about this kind of fix is that we will
never remember to drop this -std=gnu99 option once upstream fixes its
code base to be C23 compliant.
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-07-28 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 20:24 [Buildroot] [PATCH v2 1/1] package/berkeleydb: fix build with host gcc-15.x Julien Olivain via buildroot
2025-07-28 20:57 ` Thomas Petazzoni via buildroot [this message]
2025-07-28 22:20 ` Julien Olivain via buildroot
2025-07-29 7:27 ` Thomas Petazzoni via buildroot
2025-08-07 18:24 ` Thomas Perale 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=20250728225754.108b36eb@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.