From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: El Mehdi YOUNES <elmehdi.younes@smile.fr>
Cc: buildroot@buildroot.org, David Pierret <david.pierret@smile.fr>,
Romain Naour <romain.naour@smile.fr>
Subject: Re: [Buildroot] [PATCH 1/1] package/bat: fix build with GCC 15
Date: Tue, 2 Sep 2025 17:42:43 +0200 [thread overview]
Message-ID: <20250902174243.7e73b14a@windsurf> (raw)
In-Reply-To: <f834c040-70df-46dc-91b1-c50b9a91a69d@smile.fr>
On Tue, 2 Sep 2025 17:28:41 +0200
El Mehdi YOUNES <elmehdi.younes@smile.fr> wrote:
> The patch was not submitted upstream because there is already an ongoing
> discussion about removing Oniguruma from bat altogether, since Oniguruma
> has been declared archived:
>
> https://github.com/sharkdp/bat/issues/3285
>
> For now, some features in bat still depend on Oniguruma by default, so
> upstream keeps 'regex-onig' as the default engine. That’s why I did not
> propose this patch upstream.
Would be good to have this extensive explanation in the patch, instead
of just "Upstream: not submitted".
> According to the upstream discussion, it still makes sense for bat to
> keep Oniguruma as the default engine for now. So before sending a v2, I
> would like to take a step back and explore another approach.
>
> I know that 'onig_sys' can sometimes link against a system-provided
> Oniguruma library instead of compiling it. In Buildroot we
> already have 'oniguruma' available as a package, so we could consider
> using that system library rather than patching bat to switch to
> 'regex-fancy'. This way, we could keep bat aligned with upstream while
> still fixing the GCC 15 build issue. What do you think about this?
>
> see
>
> https://crates.io/crates/onig/6.5.1
That would work with me as well. What's important is that we have a GCC
15.x build fix available in the short term. Another option is to take
your quick fix as-is, and later on improve to use again Oniguruma.
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-09-02 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 13:42 [Buildroot] [PATCH 1/1] package/bat: fix build with GCC 15 El Mehdi YOUNES via buildroot
2025-09-02 13:49 ` Thomas Petazzoni via buildroot
2025-09-02 14:56 ` El Mehdi YOUNES via buildroot
2025-09-02 15:11 ` Thomas Petazzoni via buildroot
2025-09-02 15:28 ` El Mehdi YOUNES via buildroot
2025-09-02 15:42 ` Thomas Petazzoni via buildroot [this message]
2025-09-03 19:21 ` Thomas Petazzoni via buildroot
2025-09-04 15:12 ` El Mehdi YOUNES 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=20250902174243.7e73b14a@windsurf \
--to=buildroot@buildroot.org \
--cc=david.pierret@smile.fr \
--cc=elmehdi.younes@smile.fr \
--cc=romain.naour@smile.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox