All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/openscap: bump to version 1.4.3
Date: Fri, 3 Apr 2026 13:52:06 +0200	[thread overview]
Message-ID: <ac-pu604QIA40Sf3@windsurf> (raw)
In-Reply-To: <20260403-openscap_bump-v1-1-20f99c3c9429@bootlin.com>

Hello,

On Fri, Apr 03, 2026 at 11:51:52AM +0200, Alexis Lothoré wrote:
> The custom patch to enforce project as C project as been merged upstream

                                                   ^^^ has

^[[O> diff --git a/package/openscap/Config.in b/package/openscap/Config.in
> index 317055c75327..827590598e41 100644
> --- a/package/openscap/Config.in
> +++ b/package/openscap/Config.in
> @@ -10,7 +10,7 @@ config BR2_PACKAGE_OPENSCAP
>  	select BR2_PACKAGE_LIBXSLT
>  	select BR2_PACKAGE_LIBXMLSEC1
>  	select BR2_PACKAGE_MUSL_FTS if !BR2_TOOLCHAIN_USES_GLIBC
> -	select BR2_PACKAGE_PCRE
> +	select BR2_PACKAGE_PCRE2
>  	select BR2_PACKAGE_PCRE_UTF

Since you're now selecting PCRE2, it no longer makes sense to select
BR2_PACKAGE_PCRE_UTF, which is a suboption of BR2_PACKAGE_PCRE.

Thanks!

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:[~2026-04-03 11:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-03  9:51 [Buildroot] [PATCH] package/openscap: bump to version 1.4.3 Alexis Lothoré via buildroot
2026-04-03 11:52 ` Thomas Petazzoni via buildroot [this message]
2026-04-03 12:31   ` Alexis Lothoré 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=ac-pu604QIA40Sf3@windsurf \
    --to=buildroot@buildroot.org \
    --cc=alexis.lothore@bootlin.com \
    --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.