public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] meta/conf/layer.conf: Avoid adding build deps of rpm-sequoia-native
Date: Mon, 3 Nov 2025 13:29:02 +0100	[thread overview]
Message-ID: <ec0c349b-4f6e-42e8-be37-e8e8d368c931@gmail.com> (raw)
In-Reply-To: <CANNYZj9WdjNNdaNTUuhL=J_TJf51zfOONb0xR8X05QCs8ioiRQ@mail.gmail.com>

2025. 11. 03. 12:16 keltezéssel, Alexander Kanavin írta:
> On Mon, 3 Nov 2025 at 09:04, Zoltan Boszormenyi via
> lists.openembedded.org <zboszor=gmail.com@lists.openembedded.org>
> wrote:
>
>> Avoid adding dependencies of rpm-sequoia-native into sysroots
>> as it needs none of its build dependencies to run.
> This needs to be a bit more specific. What is specifically installed
> into sysroots that you would like to avoid having there?

rpm-sequoia is Rust based.

rust[-native] in Yocto master depends on llvm[-native].

The target build just uses the shlib dependencies (only libssl.so.3,
libcrypto.so.3, libgcc_s.so.1, and the C runtime), but the native build
pulls in the whole destdir for each build dependency.

So, it's not actually true that none of the build dependencies
are needed, but the openssl libs and the libgcc_s native builds
are pulled in via some other recipes that are needed in native sysroots.

Anyway, noth rust-native and llvm-native are quite heavy, so
not copying them speeds up packaging a little and saves disk space.

llvm-native also conflicts with clangXX-native builds in meta-clang-revival.

Recipes using TOOLCHAIN = "clang14" or similar build successfully,
but extend_recipe_sysroot in staging.bbclass fails when re-run
before packaging.

See my previous mail at
https://lists.openembedded.org/g/openembedded-core/message/225411

Currently this change is in the layer.conf of meta-clang-revival,
but the speedup and the disk space saving worth it to have
it in oe-core.

I will send v2 with the extended explanation and only omitting
rust-native and llvm-native.



      reply	other threads:[~2025-11-03 12:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03  8:04 [PATCH] meta/conf/layer.conf: Avoid adding build deps of rpm-sequoia-native Zoltán Böszörményi
2025-11-03 11:16 ` [OE-core] " Alexander Kanavin
2025-11-03 12:29   ` 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=ec0c349b-4f6e-42e8-be37-e8e8d368c931@gmail.com \
    --to=zboszor@gmail.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@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