From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Xu, Dongxiao" <dongxiao.xu@intel.com>
Cc: yocto <yocto@yoctoproject.org>
Subject: Re: COMPATIBLE_HOST in initramfs-live-install_1.0.bb
Date: Wed, 29 Feb 2012 10:36:32 +0000 [thread overview]
Message-ID: <1330511792.9185.149.camel@ted> (raw)
In-Reply-To: <1330498010.1785.48.camel@dongxiao-osel>
On Wed, 2012-02-29 at 14:46 +0800, Xu, Dongxiao wrote:
> I saw in initramfs-live-install_1.0.bb recipe, there is a line to set
> the COMPATIBLE_HOST:
>
> COMPATIBLE_HOST = "(i.86|x86_64).*-linux"
>
> But actually initramfs-live-install is set as dependency in
> core-image-minimal-initramfs.bb. Therefore if we set machine to be
> "qemuarm" or something else that is not x86 architecture, and then
> execute:
> # bitbake core-image-minimal-initramfs
> or
> # bitbake universe
>
> System will report an error of:
>
> ERROR: Nothing RPROVIDES
> 'initramfs-live-install' (but /home/yocto-build5/poky-contrib/meta/recipes-core/images/core-image-minimal-initramfs.bb RDEPENDS on or otherwise requires it)
> ERROR: initramfs-live-install was skipped: incompatible with host
> arm-poky-linux-gnueabi (not in COMPATIBLE_HOST)
> NOTE: Runtime target 'initramfs-live-install' is unbuildable,
> removing...
> Missing or unbuildable dependency chain was: ['initramfs-live-install']
> ERROR: Required build target 'core-image-minimal-initramfs' has no
> buildable providers.
> Missing or unbuildable dependency chain was:
> ['core-image-minimal-initramfs', 'initramfs-live-install']
>
> Summary: There was 1 WARNING message shown.
> Summary: There were 2 ERROR messages shown, returning a non-zero exit
> code.
>
> Could you help to explain the background to set compatible host for the
> initramfs-live-install recipe?
It uses syslinux which only works on IA32?
Cheers,
Richard
prev parent reply other threads:[~2012-02-29 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 6:46 COMPATIBLE_HOST in initramfs-live-install_1.0.bb Xu, Dongxiao
2012-02-29 10:36 ` Richard Purdie [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=1330511792.9185.149.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=dongxiao.xu@intel.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.