Re: [Buildroot] [PATCH v2 1/1] package/berkeleydb: fix build with host gcc-15.x

[Thomas Petazzoni via buildroot <buildroot@buildroot.org>]

Hello,

On Tue, 29 Jul 2025 00:20:14 +0200
Julien Olivain <ju.o@free.fr> wrote:

> Could we track those bulk fixes (like gcc-15 build failures) with
> comments, like we do for _AUTORECONF or _IGNORE_CVES? It's not ideal,
> but at least we could more easily do cleanups later (with git grep).
> 
> Alternatively, we could add a commented link to an upstream bug
> report. This would introduce a bit more maintenance work.
> 
> What do you think?

Yeah, I don't really have a good idea either, otherwise I would have
proposed it. A patch fixing the C23 issues is more likely to be noticed
when we bump the package, but sometimes fixing all the issues is quite
annoying. So if -std=gnu99 is added, indeed some kind of annotation
could be added. Or maybe we should "git grep std=gnu99" from time to
time, and check if it's still needed? Or remember to check this when we
merge version bumps?

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