From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: Martin Jansa <Martin.Jansa@gmail.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][PATCH 1/2] xen-tools: fix COMPATIBLE_HOST restriction for i686
Date: Tue, 3 Mar 2020 20:03:49 -0500 [thread overview]
Message-ID: <20200304010348.GB39743@gmail.com> (raw)
In-Reply-To: <20200303141036.5833-1-Martin.Jansa@gmail.com>
merged.
Bruce
In message: [meta-virtualization][PATCH 1/2] xen-tools: fix COMPATIBLE_HOST restriction for i686
on 03/03/2020 Martin Jansa wrote:
> * let TARGET_VENDOR to be set to something else than the default:
> meta/conf/bitbake.conf:TARGET_VENDOR = "-oe"
> like other architectures use
> ---
> recipes-extended/xen/xen-tools.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-extended/xen/xen-tools.inc b/recipes-extended/xen/xen-tools.inc
> index 8bdbfec..8b86f7b 100644
> --- a/recipes-extended/xen/xen-tools.inc
> +++ b/recipes-extended/xen/xen-tools.inc
> @@ -1,7 +1,7 @@
> SUMMARY = "Xen hypervisor tools"
> DESCRIPTION = "Tools and utility software for the Xen hypervisor"
>
> -COMPATIBLE_HOST = 'i686-oe-linux|(x86_64.*).*-linux|aarch64.*-linux|arm-.*-linux-gnueabi'
> +COMPATIBLE_HOST = 'i686-.*-linux|(x86_64.*).*-linux|aarch64.*-linux|arm-.*-linux-gnueabi'
>
> inherit setuptools3 update-rc.d systemd deploy
> require xen-blktap.inc
> --
> 2.20.1
>
>
next prev parent reply other threads:[~2020-03-04 1:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 14:10 [meta-virtualization][PATCH 1/2] xen-tools: fix COMPATIBLE_HOST restriction for i686 Martin Jansa
2020-03-03 14:10 ` [meta-virtualization][PATCH 2/2] xen-python2: add the same COMPATIBLE_HOST restriction as xen-tools Martin Jansa
2020-03-09 17:25 ` Christopher Clark
2020-03-04 1:03 ` Bruce Ashfield [this message]
[not found] <15F8D09CD90CE2BE.3586@lists.yoctoproject.org>
2020-03-04 15:29 ` [meta-virtualization][PATCH 1/2] xen-tools: fix COMPATIBLE_HOST restriction for i686 Martin Jansa
2020-03-04 23:05 ` Christopher Clark
2020-03-06 23:52 ` Martin Jansa
2020-03-12 0:35 ` Christopher Clark
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=20200304010348.GB39743@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=Martin.Jansa@gmail.com \
--cc=meta-virtualization@lists.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.