public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] base/bitbake.conf: Rework DISTRO_FEATURES and MACHINE_FEATURES default handling
Date: Wed, 29 Apr 2026 09:58:07 +0200	[thread overview]
Message-ID: <73dcaf57-8629-483c-935b-0abec14656d4@gmail.com> (raw)
In-Reply-To: <1d912b5e73c5ef463eaa1c7e0dfcf8607767efad.camel@linuxfoundation.org>

2026. 04. 27. 16:26 keltezéssel, Richard Purdie írta:
> On Sun, 2026-04-26 at 09:28 +0200, Böszörményi Zoltán wrote:
>> I found via git bisect that this breaks my builds.
>>
>> It breaks two things:
>>
>> 1.
>>
>> With DISTRO_FEATURES containing seccomp (e.g. when using
>> meta-virtualization and/or meta-security), this libseccomp-native
>> is not found by gnutls-native anymore. Sure enough, the libseccomp
>> recipe does not have BBCLASSEXTEND = "native nativesdk" like
>> gnutls has. So this change has at least some good points to
>> point out pre-existing issues.
>>
>> 2.
>>
>> A circular dependency occurs:
>>
>> ERROR: Task
>> virtual:native:/mnt2/zozo/yocto-6.0-arm/conf/../layers/openembedded-
>> core/meta/recipes-core/util-linux/util-
>> linux_2.41.3.bb:do_create_recipe_spdx
>> has circular dependency on
>> /mnt2/zozo/yocto-6.0-arm/conf/../layers/openembedded-
>> core/meta/recipes-core/systemd/systemd-systemctl-
>> native_259.5.bb:do_create_recipe_spdx
>> ERROR: Command execution failed: Exited with 1
>>
>> Adding INHERIT += "nospdx" does not fix this and none of
>> the layers have any bbappend that would explain this.
>>
>> Using the preceding commit fixes the build even without adding
>> the necessary BBCLASSEXTEND incantation to libseccomp.
> I tried to reproduce this by including meta-virtualization, using a
> systemd based DISTRO (poky-altcfg), setting seccomp in my
> DISTRO_FEATURES and building both util-linux-native and systemd-
> systemctl-native (and then world). I wasn't able to reproduce.
>
> How do I reproduce it?

I only found the culprit today.
I had this lingering in my custom distro layer:

DISTRO_FEATURES += "${DISTRO_FEATURES_LIBC}"

Apparently, DISTRO_FEATURES_LIBC was dropped in 2019 without me
noticing it and nothing was warning about that I was still using it.

The circular dependency problem was gone after removing this line.

Please, add this variable to the list of obsolete variables.

Thanks!



      reply	other threads:[~2026-04-29  7:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23 13:33 [PATCH 1/2] sanity.conf: Depend on bitbake 2.18 Richard Purdie
2026-04-23 13:33 ` [PATCH 2/2] base/bitbake.conf: Rework DISTRO_FEATURES and MACHINE_FEATURES default handling Richard Purdie
2026-04-26  7:28   ` [OE-core] " Böszörményi Zoltán
2026-04-27 14:26     ` Richard Purdie
2026-04-29  7:58       ` Böszörményi Zoltán [this message]

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=73dcaf57-8629-483c-935b-0abec14656d4@gmail.com \
    --to=zboszor@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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