Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: b28495@freescale.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] qemu: use PACKAGECONFIG to address libaio/attr/libcap dependencies
Date: Wed, 03 Jul 2013 14:37:57 +0100	[thread overview]
Message-ID: <3615537.9YYZDXbCb0@helios> (raw)
In-Reply-To: <1372844710-15122-1-git-send-email-b28495@freescale.com>

Hi Ting,

On Wednesday 03 July 2013 17:45:10 b28495@freescale.com wrote:
> From: Ting Liu <b28495@freescale.com>
> 
> Move to using the PACKAGECONFIG mechanism to select configure options
> and dependencies. Without this the system will attempt to discover
> various dependencies, and sometimes does so incorrectly.
> 
> Signed-off-by: Ting Liu <b28495@freescale.com>
> ---
>  meta/recipes-devtools/qemu/qemu.inc |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/meta/recipes-devtools/qemu/qemu.inc
> b/meta/recipes-devtools/qemu/qemu.inc index 7caef6e..8be3890 100644
> --- a/meta/recipes-devtools/qemu/qemu.inc
> +++ b/meta/recipes-devtools/qemu/qemu.inc
> @@ -84,6 +84,8 @@ do_install_append() {
>  # END of qemu-mips workaround
> 
>  PACKAGECONFIG ??= ""
> +PACKAGECONFIG[virtfs] = "--enable-virtfs
> --enable-attr,--disable-virtfs,libcap attr," 
> +PACKAGECONFIG[libaio] =
> "--enable-linux-aio,--disable-linux-aio,libaio,"

The latter should be "aio" and not "libaio" (since "aio" is the feature being 
enabled/disabled).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-07-03 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03  9:45 [PATCH] qemu: use PACKAGECONFIG to address libaio/attr/libcap dependencies b28495
2013-07-03 13:37 ` Paul Eggleton [this message]
2013-07-04  2:01   ` Liu Ting-B28495

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=3615537.9YYZDXbCb0@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=b28495@freescale.com \
    --cc=openembedded-core@lists.openembedded.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