All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: "Moore, Thomas (FtWorth)" <Thomas.Moore2@atk.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: COMPATIBLE_HOST
Date: Mon, 2 Feb 2015 15:21:26 +0000	[thread overview]
Message-ID: <CAJTo0La6u6w7mK3wLNZ4N+w2S-0rQmxP6HJceJr=bkUWq1-quA@mail.gmail.com> (raw)
In-Reply-To: <7B6FE55CD594D7478CED8A39DF3BFC0A5E74429D@UT40SVCWEM001.atk.com>

[-- Attachment #1: Type: text/plain, Size: 654 bytes --]

Hi Thomas,

On 2 February 2015 at 15:17, Moore, Thomas (FtWorth) <Thomas.Moore2@atk.com>
wrote:

> I have a binary recipe that is only compatible with x86 and x86_64
> systems. I *think* specifying the COMPATIBLE_HOST in my recipe would be a
> good idea. However, I've been unable to find any documentation, or even a
> good description, of this variable. Can someone help me out here?
>

The manual has a section in the glossary:

http://www.yoctoproject.org/docs/1.7.1/mega-manual/mega-manual.html#var-COMPATIBLE_HOST

And yes, this is the idiom.  Lots of meta-intel for example uses
COMPATIBLE_HOST = '(i.86|x86_64).*-linux'.

Ross

[-- Attachment #2: Type: text/html, Size: 1260 bytes --]

  reply	other threads:[~2015-02-02 15:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 15:17 COMPATIBLE_HOST Moore, Thomas (FtWorth)
2015-02-02 15:21 ` Burton, Ross [this message]
2015-02-02 15:31   ` COMPATIBLE_HOST Moore, Thomas (FtWorth)
2015-02-02 15:22 ` COMPATIBLE_HOST Gary Thomas
2015-02-02 15:28   ` COMPATIBLE_HOST Moore, Thomas (FtWorth)
2015-02-02 15:32     ` COMPATIBLE_HOST Gary Thomas
2015-02-02 15:33       ` COMPATIBLE_HOST Richard Purdie
2015-02-02 15:44         ` COMPATIBLE_HOST Gary Thomas

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='CAJTo0La6u6w7mK3wLNZ4N+w2S-0rQmxP6HJceJr=bkUWq1-quA@mail.gmail.com' \
    --to=ross.burton@intel.com \
    --cc=Thomas.Moore2@atk.com \
    --cc=yocto@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.