From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Trevor Woerner <twoerner@gmail.com>
Cc: about the oe-core layer
<Openembedded-core@lists.openembedded.org>,
Patches
Subject: Re: [PATCH] qemu.inc: Non deterministic compile of qemu
Date: Sat, 02 Mar 2013 13:02:03 +0000 [thread overview]
Message-ID: <1362229323.11004.15.camel@ted> (raw)
In-Reply-To: <CAHUNapTj+8e8fzeHt=NVQ2j5SFCZze7oVM9FqG4dRvuhB5hNDw@mail.gmail.com>
On Fri, 2013-03-01 at 11:05 -0500, Trevor Woerner wrote:
> On Fri, Mar 1, 2013 at 9:26 AM, Jason Wessel <jason.wessel@windriver.com> wrote:
> > When you using a qemuppc target and sstate you might end up with
> > the problem:
> >
> > diff --git a/meta/recipes-devtools/qemu/qemu.inc b/meta/recipes-devtools/qemu/qemu.inc
> > index 6c44b31..eb60d43 100644
> > --- a/meta/recipes-devtools/qemu/qemu.inc
> > +++ b/meta/recipes-devtools/qemu/qemu.inc
> > @@ -2,8 +2,8 @@ DESCRIPTION = "open source processor emulator"
> > HOMEPAGE = "http://qemu.org"
> > LICENSE = "GPLv2 & LGPLv2.1"
> > DEPENDS = "glib-2.0 zlib alsa-lib virtual/libx11 pixman"
> > -DEPENDS_class-native = "zlib-native alsa-lib-native glib-2.0-native pixman-native"
> > -DEPENDS_class-nativesdk = "nativesdk-zlib nativesdk-libsdl nativesdk-glib-2.0 nativesdk-pixman"
> > +DEPENDS_class-native = "zlib-native alsa-lib-native glib-2.0-native pixman-native dtc-native"
> > +DEPENDS_class-nativesdk = "nativesdk-zlib nativesdk-libsdl nativesdk-glib-2.0 nativesdk-pixman nativesdk-dtc"
> > RDEPENDS_${PN}_class-nativesdk = "nativesdk-libsdl"
>
> Is there a way to instrument this in such a way that these depends are
> included only when the target machine is qemuppc? Some sort of
> @machine_depends or something?
You could do that but it would mean you'd have a -native recipe
rebuilding when changing machine. I'd not recommend it.
Cheers,
Richard
prev parent reply other threads:[~2013-03-02 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 14:26 [PATCH] qemu.inc: Non deterministic compile of qemu Jason Wessel
2013-03-01 15:41 ` Khem Raj
2013-03-01 16:05 ` Trevor Woerner
2013-03-02 13:02 ` Richard Purdie [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=1362229323.11004.15.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=Openembedded-core@lists.openembedded.org \
--cc=twoerner@gmail.com \
/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.