All of lore.kernel.org
 help / color / mirror / Atom feed
From: "M. Asselstine" <asselsm@mcmaster.ca>
To: Christopher Clark <christopher.w.clark@gmail.com>
Cc: "meta-virtualization@yoctoproject.org"
	<meta-virtualization@yoctoproject.org>
Subject: Re: Dev86-native dependency
Date: Wed, 17 Apr 2019 08:36:57 -0400	[thread overview]
Message-ID: <CAPuovEJ6rA7j7uURyrGfHJhVENSZ8XVuzRzLhRYFrFr1o5R6tA@mail.gmail.com> (raw)
In-Reply-To: <CACMJ4GYddyoA-Q+ZB_qwR+CP+pM93kxyteKJS4cuW-4q8-eNGQ@mail.gmail.com>

On Tue, Apr 16, 2019 at 4:51 PM Christopher Clark
<christopher.w.clark@gmail.com> wrote:
>
> On Mon, Apr 15, 2019 at 6:47 PM 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?
>
> Suggest: replace the string 'dev86-native' within xen.inc's DEPENDS
> definition with:
>
> ${@bb.utils.contains('XEN_TARGET_ARCH', 'x86_64', 'dev86-native', '', d)}

Does XEN_TARGET_ARCH ever actually deviate from TARGET_ARCH? I do
prefer using the overrides as it tends to be overall more clear to
read, but the will work too.

Sathees, there isn't much to the overrides, do a 'bitbake -e xen' and
pipe the output to a file. Then search for "OVERRIDES" and you should
find a list of override words, appending one of these words to a
variable such as DEPENDS will only set the assignment if the override
is present. Read a few tutorials and examine some examples and you
should be able to sort it out rather quickly.

MarkA

>
> which will toggle the requirement for the dev86-native tools based on
> the target arch the hypervisor is being built for.
> If that looks OK, I can send a patch on top of the 4.12 version uprev
> that I just posted.
>
> Christopher
>
> >
> > 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
> > --
> > _______________________________________________
> > meta-virtualization mailing list
> > meta-virtualization@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-virtualization


  reply	other threads:[~2019-04-17 12:37 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
2019-04-16 20:51   ` Christopher Clark
2019-04-17 12:36     ` M. Asselstine [this message]
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=CAPuovEJ6rA7j7uURyrGfHJhVENSZ8XVuzRzLhRYFrFr1o5R6tA@mail.gmail.com \
    --to=asselsm@mcmaster.ca \
    --cc=christopher.w.clark@gmail.com \
    --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.