From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky Project <poky@yoctoproject.org>
Subject: Re: Can't build for qemuppc
Date: Thu, 29 Sep 2011 17:19:23 +0100 [thread overview]
Message-ID: <1317313171.12332.104.camel@ted> (raw)
In-Reply-To: <4E8498FA.3000206@mlbassoc.com>
On Thu, 2011-09-29 at 10:12 -0600, Gary Thomas wrote:
> This used to work:
>
> $ bitbake core-image-sato
> Loading cache: 100% |####################################################################################| ETA: 00:00:00
> Loaded 1034 entries from dependency cache.
>
> OE Build Configuration:
> BB_VERSION = "1.13.3"
> TARGET_ARCH = "powerpc"
> TARGET_OS = "linux"
> MACHINE = "qemuppc"
> DISTRO = "poky"
> DISTRO_VERSION = "1.0+snapshot-20110929"
> TUNE_FEATURES = "m32 fpu-hard ppc603e"
> TARGET_FPU = ""
> meta
> meta-yocto = "master:e3c5d7a90ae179af0ac128ea4dfc1a5a6602c2e4"
>
> NOTE: Resolving any missing task queue dependencies
> ERROR: Nothing PROVIDES 'syslinux'
> ERROR: syslinux was skipped: incompatible with host powerpc-poky-linux
> ERROR: Required build target 'core-image-sato' has no buildable providers.
> Missing or unbuildable dependency chain was: ['core-image-sato', 'syslinux']
>
>
> What am I doing wrong? How do I build an image to test with qemuppc,
> in particular I want to test 'web-webkit'?
I just checked here and this starts building fine. Something is pulling
"syslinux" into your build and that makes no sense as its x86 specific.
You need to figure out where that is coming from and I suspect your
local config or customisations.
Cheers,
Richard
next prev parent reply other threads:[~2011-09-29 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 16:12 Can't build for qemuppc Gary Thomas
2011-09-29 16:19 ` Richard Purdie [this message]
2011-09-29 16:40 ` 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=1317313171.12332.104.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.com \
--cc=poky@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.