Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Vincent Davis Jr" <vince@underview.tech>
To: openembedded-devel@lists.openembedded.org
Subject: coreutils over uutils-coreutils when selinux in DISTRO_FEATURES
Date: Sat, 30 Dec 2023 17:29:18 -0800	[thread overview]
Message-ID: <0nJP.1703986158117153552.ibjv@lists.openembedded.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]

Hello all,

Currently using coreutils over busybox and systemd over sysvinit via:

> 
> 
> 
> 
> SKIP_RECIPE[busybox] = "Don't build this"
> DISTRO_FEATURES_BACKFILL_CONSIDERED:append = " sysvinit"
> VIRTUAL-RUNTIME_syslog = ""
> VIRTUAL-RUNTIME_initscripts = ""
> VIRTUAL-RUNTIME_init_manager = "systemd"
> VIRTUAL-RUNTIME_dev_manager = "udev"
> VIRTUAL-RUNTIME_login_manager = "shadow-base"
> VIRTUAL-RUNTIME_base-utils = "packagegroup-core-base-utils"
> VIRTUAL-RUNTIME_base-utils-hwclock = "util-linux-hwclock"
> VIRTUAL-RUNTIME_base-utils-syslog = ""
> VIRTUAL-RUNTIME_vim = "vim"
> PREFERRED_PROVIDER_udev = "systemd"
> PREFERRED_PROVIDER_udev-utils = "systemd"
> PREFERRED_PROVIDER_virtual/base-utils = "packagegroup-core-base-utils"
> PREFERRED_PROVIDER_coreutils = "coreutils"
> 
> 

Need help determining how to use coreutils over uutils-coreutils?
uutils-coreutils only gets built when I include "selinux" in *DISTRO_FEATURES.
* Thus it leads me to

ERROR: Nothing PROVIDES 'clang-native'
ERROR: Nothing RPROVIDES 'uutils-coreutils'

Of course happens because I'm not including meta-clang.

I've bypassed error by including:

SKIP_RECIPE[uutils-coreutils] = "Don't build this"
BBMASK += "/meta-oe/recipes-core/uutils-coreutils"

Which builds, but doesn't include required tools into target system image
sed,which.

I have tried removing SKIP_RECIPE,BBMASK and set

PREFERRED_PROVIDER_coreutils = "coreutils"

Still wants to build uutils-coreutils over coreutils.

I would like to not include meta-clang and of course not use uutils-coreutils over coreutils.

[-- Attachment #2: Type: text/html, Size: 1778 bytes --]

             reply	other threads:[~2023-12-31  1:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-31  1:29 Vincent Davis Jr [this message]
2023-12-31 23:18 ` coreutils over uutils-coreutils when selinux in DISTRO_FEATURES Vincent Davis Jr
2024-10-10 20:06   ` Clayton Casciato
2024-11-03 17:13     ` Vincent Davis Jr
2026-03-25 23:30       ` [oe] " Clayton Casciato
2026-03-26  0:53         ` Khem Raj

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=0nJP.1703986158117153552.ibjv@lists.openembedded.org \
    --to=vince@underview.tech \
    --cc=openembedded-devel@lists.openembedded.org \
    /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