From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Chen, Qi" <Qi.Chen@windriver.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH V3 1/5] classes/recipes: remove unnecessary qemu inherit and use qemuwrapper-cross
Date: Thu, 17 Apr 2025 11:11:14 +0100 [thread overview]
Message-ID: <95a4ea27c60ac88b47ed68d69c6085179fccf9fd.camel@linuxfoundation.org> (raw)
In-Reply-To: <CO6PR11MB5602D61A318C6EA7C9E1826EEDBC2@CO6PR11MB5602.namprd11.prod.outlook.com>
On Thu, 2025-04-17 at 02:26 +0000, Chen, Qi wrote:
> Got it. I'll look into the problem ASAP.
I did look into it a bit and the issue seems to be that fontcache
recipes are allarch but can call into qemu to run fc-cache. An allarch
recipe can't depend on qemuwrapper-cross since that is target specific.
I guess we may need to exclude the dependency in layer.conf.
Cheers,
Richard
next prev parent reply other threads:[~2025-04-17 10:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 5:34 [OE-core][PATCH V3 1/5] classes/recipes: remove unnecessary qemu inherit and use qemuwrapper-cross Qi.Chen
2025-04-14 5:35 ` [OE-core][PATCH V3 2/5] cpio: fix ptest-runner dependency Qi.Chen
2025-04-17 11:42 ` Ross Burton
2025-04-14 5:35 ` [OE-core][PATCH V3 3/5] nativesdk.bbclass: handle PACKAGE_WRITE_DEPS Qi.Chen
2025-04-14 5:35 ` [OE-core][PATCH V3 4/5] image/populate_sdk.bbclass: drop qemuwrapper-cross from DEPENDS Qi.Chen
2025-04-14 5:35 ` [OE-core][PATCH V3 5/5] lib/classes/recipes: refactor qemu.bbclass functions into library functions Qi.Chen
2025-04-16 16:55 ` [OE-core][PATCH V3 1/5] classes/recipes: remove unnecessary qemu inherit and use qemuwrapper-cross Richard Purdie
2025-04-17 2:26 ` Chen, Qi
2025-04-17 10:11 ` Richard Purdie [this message]
2025-04-20 4:09 ` Chen, Qi
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=95a4ea27c60ac88b47ed68d69c6085179fccf9fd.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Qi.Chen@windriver.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