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 1/2] package/openscap: fix dependencies doc
Date: Wed, 4 Mar 2026 19:04:40 +0100	[thread overview]
Message-ID: <aahz7zuui_SfAImd@windsurf> (raw)
In-Reply-To: <20260304-openscap_nptl_threads-v1-1-9dff92cc37e0@bootlin.com>

On Wed, Mar 04, 2026 at 09:22:39AM +0100, Alexis Lothoré wrote:
> The comment displayed in menuconfig for openscap when we are lacking
> dependencies is currently broken: it should be an or of inverted
> expected values.
> 
> Update the comment for openscap when it is missing some dependency.
> 
> Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
> ---
>  package/openscap/Config.in | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/package/openscap/Config.in b/package/openscap/Config.in
> index 317055c75327..b5f809315c91 100644
> --- a/package/openscap/Config.in
> +++ b/package/openscap/Config.in
> @@ -19,6 +19,5 @@ config BR2_PACKAGE_OPENSCAP
>  	  https://www.open-scap.org/
>  	  https://github.com/OpenSCAP/openscap
>  
> -comment "openscap needs a toolchain w/ dynamic library"
> -	depends on BR2_PACKAGE_LIBGPG_ERROR_ARCH_SUPPORTS
> -	depends on BR2_STATIC_LIBS
> +comment "openscap needs libgpg-error and a toolchain w/ dynamic library"
> +	depends on !BR2_PACKAGE_LIBGPG_ERROR_ARCH_SUPPORTS || BR2_STATIC_LIBS

Sorry, but the existing comment is correct. We want to show the
comment when we're on an architecture that we can support, but the
toolchain lacks some features.

So as far as I can see the existing code is correct, and your patch
changes it to be incorrect :-/

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-03-04 18:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04  8:22 [Buildroot] [PATCH 0/2] package/openscap: fix build failure for openscap Alexis Lothoré via buildroot
2026-03-04  8:22 ` [Buildroot] [PATCH 1/2] package/openscap: fix dependencies doc Alexis Lothoré via buildroot
2026-03-04 18:04   ` Thomas Petazzoni via buildroot [this message]
2026-03-04 19:31     ` Alexis Lothoré via buildroot
2026-03-04  8:22 ` [Buildroot] [PATCH 2/2] package/openscap: add dependency on NPTL threads Alexis Lothoré via buildroot
2026-03-04 18:06   ` Thomas Petazzoni 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=aahz7zuui_SfAImd@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.