From: JC <jc@vtkloud.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: raspberry layer
Date: Thu, 05 Sep 2013 10:08:14 +0200 [thread overview]
Message-ID: <52283BEE.9020504@vtkloud.com> (raw)
In-Reply-To: <CANyK_8f0bwoB8sd6PdN4ZV=bZtw6E-6AqQAQnMB9j7QgAypmtA@mail.gmail.com>
On 05/09/2013 10:04, Paul Barker wrote:
> On 5 September 2013 08:55, JC <jc@vtkloud.com> wrote:
>> As a reference, following this link
>> http://www.pimpmypi.com/blog/blogPost.php?blogPostID=7 I got successful
>> (well the image is not yet finished but I hadn't that specific parsing
>> error)
>>
>> I followed the exact README steps in a fresh directory for the checkout, so
>> I am on the trunk for poky & meta-raspberrypi...
>>
> The log you've attached shows paths for poky as well as
> openembedded-core. Poky is basically a combination of
> openembedded-core, meta-yocto and bitbake so you don't want to add
> openembedded-core again. Could you post your full bblayers.conf?
>
Yes that's strange. Do you think it could be an issue with trunk ?
Here's my bblayers:
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "6"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/media/yocto/yocto/poky/meta \
/media/yocto/yocto/poky/meta-yocto \
/media/yocto/yocto/poky/meta-yocto-bsp \
/media/yocto/yocto/meta-openembedded/meta-oe \
/media/yocto/yocto/meta-raspberrypi \
"
BBLAYERS_NON_REMOVABLE ?= " \
/media/yocto/yocto/poky/meta \
/media/yocto/yocto/poky/meta-yocto \
"
next prev parent reply other threads:[~2013-09-05 8:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 16:40 raspberry layer JC
2013-09-04 16:46 ` Gary Thomas
2013-09-05 7:21 ` JC
2013-09-05 7:31 ` Paul Barker
2013-09-05 7:55 ` JC
2013-09-05 8:04 ` Paul Barker
2013-09-05 8:08 ` JC [this message]
2013-09-05 8:12 ` Paul Barker
2013-09-05 8:20 ` JC
2013-09-05 8:28 ` Paul Eggleton
2013-09-05 9:07 ` JC
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=52283BEE.9020504@vtkloud.com \
--to=jc@vtkloud.com \
--cc=paul@paulbarker.me.uk \
--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.