From: "Weisser, Pascal.ext" <Pascal.Weisser.ext@karlstorz.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] Resolve YOCTO #14520 and YOCTO #15525
Date: Fri, 28 Mar 2025 02:21:06 -0700 [thread overview]
Message-ID: <28798.1743153666896975321@lists.openembedded.org> (raw)
In-Reply-To: <D8K50W97LGL8.1WRT66MJ5ZYV1@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
Hi,
the problem arises because the dependency on virtual/kernel is added to the initramfs-image image, too, leading to a circular dependency loop. In our setup the problem didn't occur because we're building the initramfs-image in a different multi-configuration. That way the kernel depends on the initramfs-image from a different multi-configuration and no circular dependency loop is created.
To fix the issue we'd need a way to add the dependency on virtual/kernel to the do_write_qemuboot_conf task only only if we're not building an initramfs-image. But I have no idea at the moment how we could distinguish that case? Are there any ideas on that?
Best regards
Pascal
[-- Attachment #2: Type: text/html, Size: 791 bytes --]
prev parent reply other threads:[~2025-03-28 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 10:48 [PATCH 0/3] Resolve YOCTO #14520 and YOCTO #15525 Weisser, Pascal
2025-03-18 10:48 ` [PATCH 1/3] Revert "qemuboot: Trigger write_qemuboot_conf task on changes of kernel image realpath" Weisser, Pascal
2025-03-18 10:48 ` [PATCH 2/3] qemuboot: Trigger do_write_qemuboot_conf task on bundled initramfs changes Weisser, Pascal
2025-03-18 10:48 ` [PATCH 3/3] qemuboot: Provide default value for INITRAMFS_LINK_NAME Weisser, Pascal
2025-03-19 9:33 ` [OE-core] [PATCH 0/3] Resolve YOCTO #14520 and YOCTO #15525 Mathieu Dubois-Briand
2025-03-28 9:21 ` Weisser, Pascal.ext [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=28798.1743153666896975321@lists.openembedded.org \
--to=pascal.weisser.ext@karlstorz.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