All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Khem Raj <raj.khem@gmail.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: rpm-sequoia-native issue Re: [OE-core] llvm-native is pulled into package builds that do not rely on it
Date: Tue, 28 Oct 2025 15:20:01 +0100	[thread overview]
Message-ID: <921ee01c-e264-4e29-a424-ec294b7f2903@gmail.com> (raw)
In-Reply-To: <18729CC0E7CCD2F0.436@lists.openembedded.org>

2025. 10. 28. 10:12 keltezéssel, Zoltan Boszormenyi via lists.openembedded.org írta:
> Hi,
>
> I am trying to make my meta-clang-revival layer compatible
> with Yocto 5.3 that merged meta-clang and llvm is split off
> into its own recipe.
>
> Target recipes that use LLVM 14 or 15 (most notably, variants of
> intel-compute-runtime and their dependencies) fail with
> conflicting files being copied into recipe-sysroot-native,
> like static libs from clang14-native and llvm-native, etc.
>
> As far as I can tell, the issue occurs during packaging, after
> compilation already succeeded. The dependency chain is correct,
> otherwise the issue would occur during do_prepare_recipe_sysroot.
>
> It seems that the python function "extend_recipe_sysroot" is re-run
> for packaging. That's when it fails because llvm-native is pulled in,
> because llvm-native conflicts with e.g. clang14-native.
>
> Is it because I use signed rpm packaging?

Apparently, yes.

> rpm-sequoia-native, while it depends on rust-native, and as a
> consequence, depends on llvm-native to build, requires neither to run.
>
> How can I avoid this problem without switching to non-signed rpms?

I found the solution:

SSTATE_EXCLUDEDEPS_SYSROOT = "\
     rpm-sequoia-native->.* \
"

I have added this to my repo's layer.conf.

It may be useful for including in oe-core, or maybe not.

Only recipes depending on older clangNN versions in my
meta-clang-revival trigger the problem.

> Thanks in advance,
> Zoltán Böszörményi
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#225383): https://lists.openembedded.org/g/openembedded-core/message/225383
> Mute This Topic: https://lists.openembedded.org/mt/115990504/3617728
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [zboszor@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>



           reply	other threads:[~2025-10-28 14:20 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <18729CC0E7CCD2F0.436@lists.openembedded.org>]

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=921ee01c-e264-4e29-a424-ec294b7f2903@gmail.com \
    --to=zboszor@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --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 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.