From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] qemu-nativesdk: fix the build failure that linux/kvm.h not found
Date: Wed, 18 Jul 2012 17:01:08 -0700 [thread overview]
Message-ID: <50074E44.50503@linux.intel.com> (raw)
In-Reply-To: <1342572286-18552-1-git-send-email-yao.zhao@windriver.com>
On 07/17/2012 05:44 PM, Yao Zhao wrote:
> qemu.inc: on older kernel build hosts that have < 2.6.20 which
> doesn't support kvm yet, build will fail. Add a check in do_configure
> to make sure whether linux/kvm.h exists for nativesdk build.
>
> Signed-off-by: Yao Zhao <yao.zhao@windriver.com>
> ---
> meta/recipes-devtools/qemu/qemu.inc | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-devtools/qemu/qemu.inc b/meta/recipes-devtools/qemu/qemu.inc
> index 707493e..713674e 100644
> --- a/meta/recipes-devtools/qemu/qemu.inc
> +++ b/meta/recipes-devtools/qemu/qemu.inc
> @@ -22,8 +22,9 @@ inherit autotools
> do_configure() {
> # Handle distros such as CentOS 5 32-bit that do not have kvm support
> KVMOPTS="--disable-kvm"
> - if [ "${PN}" != "qemu-native" ] || [ -f /usr/include/linux/kvm.h ] ; then
> - KVMOPTS="--enable-kvm"
> + if [ "${PN}" != "qemu-native" -a "${PN}" != "qemu-nativesdk" ] \
> + || [ -f /usr/include/linux/kvm.h ] ; then
> + KVMOPTS="--enable-kvm"
> fi
>
> ${S}/configure --prefix=${prefix} --sysconfdir=${sysconfdir} --disable-strip ${EXTRA_OECONF} $KVMOPTS
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-07-19 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 0:44 [PATCH] qemu-nativesdk: fix the build failure that linux/kvm.h not found Yao Zhao
2012-07-19 0:01 ` Saul Wold [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=50074E44.50503@linux.intel.com \
--to=sgw@linux.intel.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 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.