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 15:49:36 +0200 [thread overview]
Message-ID: <20250902154936.1563f079@windsurf> (raw)
In-Reply-To: <20250902134250.622347-1-elmehdi.younes@smile.fr>
Hello,
Thanks for your patch!
On Tue, 2 Sep 2025 15:42:50 +0200
El Mehdi YOUNES <elmehdi.younes@smile.fr> wrote:
> Bat pulls in the onig crate (version 6.4.0) through syntect with the
> default "regex-onig" feature. This crate depends on the Oniguruma C
> library (via onig_sys), which fails to build with GCC 15 due to C23
> keyword conflicts. Newer versions of onig fix this issue, but bat
> cannot directly update the onig version because it is pinned by syntect.
>
> To resolve the build failure, apply a patch that replaces the
> "regex-onig" feature with "regex-fancy" in bat's minimal-application
> feature set. This switches bat to use the pure-Rust fancy-regex engine
> instead of Oniguruma, avoiding the problematic onig_sys dependency.
>
> Fixes:
>
> https://autobuild.buildroot.net/?reason=bat-%
This link doesn't make sense as it can contain failures unrelated to
this one, especially in the future. You need to include the link to one
specific build result.
> diff --git a/package/bat/0001-Replace-regex-onig-by-regex-fancy-in-minimal-applica.patch b/package/bat/0001-Replace-regex-onig-by-regex-fancy-in-minimal-applica.patch
> new file mode 100644
> index 0000000000..6d13c406cc
> --- /dev/null
> +++ b/package/bat/0001-Replace-regex-onig-by-regex-fancy-in-minimal-applica.patch
> @@ -0,0 +1,40 @@
> +From 9b6727df25e45222b3863dbe5f5bc58237b68ab9 Mon Sep 17 00:00:00 2001
> +From: El Mehdi YOUNES <elmehdi.younes@smile.fr>
> +Date: Tue, 2 Sep 2025 14:02:11 +0200
> +Subject: [PATCH] Replace regex-onig by regex-fancy in minimal-application
> +
> +The default "application" feature enables "minimal-application", which
> +in turn pulls in the "regex-onig" feature of syntect. This brings in the
> +onig crate (version 6.4.0) and its dependency onig_sys, which fail to
> +build with GCC 15 due to C23 keyword conflicts.
> +
> +It is not possible to simply update the onig crate from bat itself,
> +since its version is pinned indirectly by syntect. To avoid this
> +dependency and fix the build, replace "regex-onig" with "regex-fancy" in
> +"minimal-application". This makes bat use the pure-Rust fancy-regex
> +engine instead of Oniguruma, removing the need for onig_sys and allowing
> +the package to build with GCC 15.
> +
> +Upstream: not submitted
Why?
> +diff --git a/Cargo.toml b/Cargo.toml
> +index 80d19321..93a07a1d 100644
> +--- a/Cargo.toml
> ++++ b/Cargo.toml
> +@@ -29,7 +29,7 @@ minimal-application = [
> + "clap",
> + "etcetera",
> + "paging",
> +- "regex-onig",
> ++ "regex-fancy",
> + "wild",
> + ]
Are you sure this works? Patches are applied *after* the download step,
during which we do the Cargo vendoring. Also, if you pull in more
dependencies, I would expect the hash of the tarball to change, since
we hash the tarball after Cargo vendoring.
Am I missing something here?
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 13:49 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 [this message]
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
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=20250902154936.1563f079@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