Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Adam Duskett <adam.duskett@amarulasolutions.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 03/10] package/openssh: fix dependencies with refpolicy
Date: Wed, 7 Feb 2024 12:27:26 +0100	[thread overview]
Message-ID: <20240207122726.2aa4be3c@windsurf> (raw)
In-Reply-To: <0fab83c33d4c5d4afe807e78169f68d539bcf5af.1706448055.git.yann.morin.1998@free.fr>

Hello,

On Sun, 28 Jan 2024 14:20:52 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> Commit 2c5a82a29ceb(package/openssh: select linux-pam if refpolicy
> upstream is selected) did not account for the linux-pam dependencies
> before selecting it, causing unmet dependencies warnings (unfortunately,
> not errors), such as:
> 
>     $ KCONFIG_SEED=0x8D55903B make randconfig
>     WARNING: unmet direct dependencies detected for BR2_PACKAGE_LIBABSEIL_CPP
>       Depends on [n]: BR2_INSTALL_LIBSTDCPP [=y] && BR2_TOOLCHAIN_GCC_AT_LEAST_8 [=y] && BR2_TOOLCHAIN_HAS_THREADS [=y] && !BR2_STATIC_LIBS [=n] && BR2_PACKAGE_LIBABSEIL_CPP_ARCH_SUPPORTS [=n]
>       Selected by [y]:
>       - BR2_PACKAGE_RE2 [=y] && BR2_INSTALL_LIBSTDCPP [=y] && BR2_TOOLCHAIN_GCC_AT_LEAST_8 [=y] && BR2_TOOLCHAIN_HAS_THREADS [=y]

Seems like this was copy/pasted from the wrong error :-)

Also, as we discussed during the meeting, it seems like we want to:

- Move this select to the refpolicy package

- Handle it as a "soft select" that selects linux-pam if possible, to
  not have some crazy dependencies for a quite corner case (using
  SELinux non a non-glibc system, with a toolchain missing
  locale/wchar, etc.)

Could you rework according to our discussion?

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:[~2024-02-07 11:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-28 13:20 [Buildroot] [PATCH 00/10] package: fix unmet dependencies (branch yem/misc-fixes) Yann E. MORIN
2024-01-28 13:20 ` [Buildroot] [PATCH 01/10] package/util-linux: propagate linux-pam dependencies Yann E. MORIN
2024-02-07 10:41   ` Thomas Petazzoni via buildroot
2024-01-28 13:20 ` [Buildroot] [PATCH 02/10] package/ivi-homescreen: fix dependencies for gstreamer plugin Yann E. MORIN
2024-02-03 13:01   ` Adam Duskett
2024-02-07 10:41   ` Thomas Petazzoni via buildroot
2024-01-28 13:20 ` [Buildroot] [PATCH 03/10] package/openssh: fix dependencies with refpolicy Yann E. MORIN
2024-02-07 11:27   ` Thomas Petazzoni via buildroot [this message]
2024-01-28 13:20 ` [Buildroot] [PATCH 04/10] package/re2: propagate dependencies from libabseil-cpp Yann E. MORIN
2024-02-07 11:50   ` Thomas Petazzoni via buildroot
2024-01-28 13:20 ` [Buildroot] [PATCH 05/10] package/petitboot: fix ordering of comments and sub-options Yann E. MORIN
2024-02-07 11:51   ` Thomas Petazzoni via buildroot
2024-01-28 13:20 ` [Buildroot] [PATCH 06/10] package/petitboot: propagate depednencies from kexec/kexec-lite Yann E. MORIN
2024-02-07 14:25   ` Thomas Petazzoni via buildroot
2024-01-28 13:20 ` [Buildroot] [PATCH 07/10] package/python-ml-dtypes: propagate dependencies from numpy, pybind Yann E. MORIN
2024-02-07 14:26   ` Thomas Petazzoni via buildroot
2024-01-28 13:20 ` [Buildroot] [PATCH 08/10] package/opencv4: propagate internal dependencies Yann E. MORIN
2024-02-07 14:55   ` Thomas Petazzoni via buildroot
2024-01-28 13:20 ` [Buildroot] [PATCH 09/10] package/opencv-contrib: propagate opencv4 dependencies Yann E. MORIN
2024-02-07 14:55   ` Thomas Petazzoni via buildroot
2024-01-28 13:20 ` [Buildroot] [PATCH 10/10] package/atkmm: propagate dependency from at-spi2-core Yann E. MORIN
2024-02-07 10:34   ` 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=20240207122726.2aa4be3c@windsurf \
    --to=buildroot@buildroot.org \
    --cc=adam.duskett@amarulasolutions.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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