From: Sathees Balya <Sathees.Balya@arm.com>
To: "M. Asselstine" <asselsm@mcmaster.ca>
Cc: "meta-virtualization@yoctoproject.org"
<meta-virtualization@yoctoproject.org>
Subject: Re: Dev86-native dependency
Date: Tue, 16 Apr 2019 10:28:54 +0000 [thread overview]
Message-ID: <08776DD3-ECE4-414F-8334-14C36ADB4CC2@arm.com> (raw)
In-Reply-To: <CAPuovELwBEHwrU=jYFak2HqwcyXtSDspCDuKi2HSWAydLrUm=A@mail.gmail.com>
Hi,
Yes. Your understanding is correct. I would like to drop the "dev86-native" from DEPENDS and add it only for x86 architecture. However I am not familiar with the overrides mechanism.
Regards,
Sathees
On 16/04/2019, 02:46, "M. Asselstine" <asselsm@mcmaster.ca> wrote:
On Mon, Apr 15, 2019 at 9:05 PM Sathees Balya <Sathees.Balya@arm.com> wrote:
>
> Hi,
>
>
>
> The xen recipe has a hard dependency on dev86-native package (meta-virtualization/recipes-extended/xen/xen.inc). It does not allow us to build for aarch64 natively for Arm. At the moment, we have a workaround in the bbappend file for xen to remove the dependency.
>
>
>
> DEPENDS_remove = "dev86-native"
>
>
>
> Can the recipe be made generic so that both x86 and Arm can be built without the need for the above workaround? Thanks.
>
I am not sure I am following you correctly. But I believe what you are
looking for is to drop "dev86-native" from DEPENDS, where it is
currently listed, and instead list it in something like
DEPENDS_x86 = "dev86-native"
in the xen.inc file. ie. make use of the overrides mechanism to only
require it for x86 arch. Am I close?
MarkA
>
>
>
>
> Regards,
>
> Sathees
>
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
> --
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
next prev parent reply other threads:[~2019-04-17 22:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 15:50 Dev86-native dependency Sathees Balya
2019-04-16 1:46 ` M. Asselstine
2019-04-16 10:28 ` Sathees Balya [this message]
2019-04-16 20:51 ` Christopher Clark
2019-04-17 12:36 ` M. Asselstine
2019-04-17 16:38 ` Sathees Balya
2019-04-17 17:32 ` Mark Asselstine
2019-04-18 13:30 ` Bruce Ashfield
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=08776DD3-ECE4-414F-8334-14C36ADB4CC2@arm.com \
--to=sathees.balya@arm.com \
--cc=asselsm@mcmaster.ca \
--cc=meta-virtualization@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 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.