From: Ross Burton <Ross.Burton@arm.com>
To: Yocto-mailing-list <yocto@lists.yoctoproject.org>,
"richard.danter@windriver.com" <richard.danter@windriver.com>
Subject: Re: [yocto] Forbidden host packages?
Date: Tue, 30 Apr 2024 10:36:22 +0000 [thread overview]
Message-ID: <BF35EDE7-E641-4A67-9503-3757509B760D@arm.com> (raw)
In-Reply-To: <5099ede3b255d8d36fdec025c39b466aa8bd31ef.camel@windriver.com>
On 29 Apr 2024, at 18:09, Danter, Richard via lists.yoctoproject.org <richard.danter=windriver.com@lists.yoctoproject.org> wrote:
>
> On Mon, 2024-04-29 at 17:53 +0100, Richard Purdie wrote:
>> CAUTION: This email comes from a non Wind River email account!
>> Do not click links or open attachments unless you recognize the
>> sender and know the content is safe.
>>
>> On Mon, 2024-04-29 at 16:37 +0000, Danter, Richard via
>> lists.yoctoproject.org wrote:
>>> I know there are host packages which are required in order to build
>>> Yocto, but are there any that are forbidden?
>>>
>>> For example, I have encountered a build issue on a RHEL host, but
>>> only
>>> if the daxctl-devel package is installed on that host. Without it,
>>> the
>>> build works fine.
>>>
>>> The failure is in building qemu, see below.
>>
>> qemu-system-native is a little special in that it needs to interface
>> to
>> the host graphics so it has wider search paths than most packages.
>>
>> We try to explicitly disable dependencies we don't use so this sounds
>> like some configuration for this one is missing.
>
> Thanks, we will investigate further.
This is usually solved trivially by adding another PACKAGECONFIG to the qemu recipe, and not enabling it (so it gets disabled explicitly), for example:
https://git.yoctoproject.org/poky/commit/meta/recipes-devtools/qemu/qemu.inc?id=9a02fb66c23b40911b5b431b348a2e7f8a2fedfc
Ross
prev parent reply other threads:[~2024-04-30 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 16:37 Forbidden host packages? Danter, Richard
2024-04-29 16:53 ` [yocto] " Richard Purdie
2024-04-29 17:09 ` Danter, Richard
2024-04-30 10:36 ` Ross Burton [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=BF35EDE7-E641-4A67-9503-3757509B760D@arm.com \
--to=ross.burton@arm.com \
--cc=richard.danter@windriver.com \
--cc=yocto@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).