From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: Re: [PATCH 1/1] qemu: use PACKAGECONFIG to address nss dependencies
Date: Fri, 01 Nov 2013 08:50:56 +0000 [thread overview]
Message-ID: <1383295856.25877.124.camel@ted> (raw)
In-Reply-To: <52724411.9050909@windriver.com>
On Thu, 2013-10-31 at 19:50 +0800, Hongxu Jia wrote:
> On 10/31/2013 06:41 PM, Martin Jansa wrote:
> > On Thu, Oct 31, 2013 at 06:23:01PM +0800, Hongxu Jia wrote:
> >> Use PACKAGECONFIG to explicitly address nss dependencies rather than
> >> tested by configure.
> >>
> >> It avoided potential errors while multiple builds shared a common
> >> state_cache.
> > There are more floating dependencies in qemu.inc, see
> > http://patchwork.openembedded.org/patch/56935/
> >
> > and even this list isn't complete, there is also:
> > WARN: packages/armv5te-oe-linux-gnueabi/qemu/qemu/latest lost dependency on cairo gdk-pixbuf gnutls gtk+ libvte
> >
> > Can you please improve it to fix them all?
> >
>
> OK, I will try to fix them as possible as I can.
>
> Drop this patch, wait for V2.
Part of the problem here is that qemu-native has some "floating"
dependencies by design. If the native system has graphics support, qemu
will have too. If it doesn't it won't have. This works out to be quite
useful for people. Some people have headless build machines they don't
want to install X on, equally some have build machines which do have X
and they do want graphical qemu.
How do we support both?
Cheers,
Richard
next prev parent reply other threads:[~2013-11-01 8:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 10:23 [PATCH 0/1] qemu: use PACKAGECONFIG to address nss dependencies Hongxu Jia
2013-10-31 10:23 ` [PATCH 1/1] " Hongxu Jia
2013-10-31 10:41 ` Martin Jansa
2013-10-31 11:50 ` Hongxu Jia
2013-11-01 8:50 ` Richard Purdie [this message]
2013-11-01 9:39 ` Martin Jansa
2013-11-01 10:52 ` Richard Purdie
2013-11-01 11:42 ` Hongxu Jia
2013-11-01 12:16 ` Martin Jansa
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=1383295856.25877.124.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=saul.wold@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox