Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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:11:44 +0200	[thread overview]
Message-ID: <20250902171144.479f13a6@windsurf> (raw)
In-Reply-To: <cdae50eb-2553-4baf-ac3d-450838705c32@smile.fr>

On Tue, 2 Sep 2025 16:56:59 +0200
El Mehdi YOUNES <elmehdi.younes@smile.fr> wrote:

> > 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.  
> I can fix this in a v2 if needed.

👍️

> >> +Upstream: not submitted  
> > Why?  
> 
> Do you mean why we are switching from 'regex-onig' to 'regex-fancy',
> 
> or why the patch has not been submitted upstream?

Why the patch was not submitted upstream.

> In this patch, I switched the feature from 'regex-onig' to 'regex-fancy'.
> This does not affect vendoring in our case, since vendoring is based on
> Cargo.lock. In the current Cargo.lock, 'syntect' already lists both
> 'fancy-regex' and 'onig' as dependencies. Therefore, the set of crates
> included in vendoring remains exactly the same before and after the patch
> (I tested this locally).
> 
> What really changes is only at compile time: after the patch, Cargo builds
> with 'fancy-regex' instead of 'onig'/'onig_sys'.
> 
> Do you think I should avoid this approach? If so, I can look into another
> ways to fix this

Aaah, makes sense. I was not aware of this mechanism. Sounds good.
Could you submit a v2 to fix the other minor issues?

Thanks a lot!

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

  reply	other threads:[~2025-09-02 15:12 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 [this message]
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=20250902171144.479f13a6@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