From: Martin Jansa <martin.jansa@gmail.com>
To: "Hans Beckérus" <hans.beckerus@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: meta-openembedded/meta-oe and busbox issues in 'dora'
Date: Mon, 4 Nov 2013 17:11:12 +0100 [thread overview]
Message-ID: <20131104161112.GE3684@jama> (raw)
In-Reply-To: <CAFyqS9pSWH5Lee1xTCKmj8gTLYrQRgk340a-UcYTjWsGj+wjfw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
On Mon, Nov 04, 2013 at 05:05:43PM +0100, Hans Beckérus wrote:
> Hello. We get the below error when trying to build our image in Yocto
> 1.5 'dora'.
>
> ERROR: No recipes available for:
> /home/poky/meta-openembedded/meta-oe/recipes-core/busybox/busybox_1.20.2.bbappend
> ERROR: Command execution failed: Exited with 1
>
> We use the 'dora' branch also in meta-openembedded.
Why are you using meta-openembedded from 'dora' branch when your oe-core
branch is 'master'?
Use the same branches for all layers.
> But busybox has been upgraded to 1.21.1 in Yocto. Is there some simple
> way to workaround this issue (besides removing the busybox recipe from
> meta-oe)?
> I.e is there some clean way to tell bitbake that it is expected that
> this specific recipe is missing?
>
> Thanks.
> Hans
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-11-04 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 16:05 meta-openembedded/meta-oe and busbox issues in 'dora' Hans Beckérus
2013-11-04 16:11 ` Martin Jansa [this message]
2013-11-04 16:21 ` Hans Beckérus
2013-11-04 16:36 ` Stanacar, StefanX
2013-11-04 16:41 ` Hans Beckérus
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=20131104161112.GE3684@jama \
--to=martin.jansa@gmail.com \
--cc=hans.beckerus@gmail.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.