All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: yocto@yoctoproject.org
Subject: Re: Raspberry pi build with gstreamer1.0 error - No recipes avalible.
Date: Sat, 11 Mar 2017 16:59:29 -0800	[thread overview]
Message-ID: <9c9bd988-e130-c48e-e8e4-e0c51da151f3@gmail.com> (raw)
In-Reply-To: <SG2PR0301MB20164EBE7DDD10BD3A4BFE69D1230@SG2PR0301MB2016.apcprd03.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 1015 bytes --]



On 3/11/17 5:19 AM, Steve Plant wrote:
> Hi all,
> 
> Starting a brand new project for the rasberry pi2, on the master branch, using toaster to start/monitor the build.
> 
> Everything set up for the most basic build, however when I build "rpi-basic-image" it fails with this error:
> 
> No recipes available for:
>   /home/steve/Yocto/poky/_toaster_clones/_git___git.yoctoproject.org_meta-raspberrypi_master/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.2.0.bbappend
>   /home/steve/Yocto/poky/_toaster_clones/_git___git.yoctoproject.org_meta-raspberrypi_master/recipes-multimedia/gstreamer/gstreamer1.0-omx_git.bbappend
> 
> 
> Looking through some of the recent changes on this mailing list, the
> gstreamer1.0 package got a change recently. has anybody else come across
> this error?
> 
> 

Its a known problem

Please use kraj/master branch from https://github.com/kraj/meta-raspberrypi

for now. I will send a pull request tonight for upstream.

> 
> Regards, Steve.
> 
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

      reply	other threads:[~2017-03-12  0:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-11 13:19 Raspberry pi build with gstreamer1.0 error - No recipes avalible Steve Plant
2017-03-12  0:59 ` Khem Raj [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=9c9bd988-e130-c48e-e8e4-e0c51da151f3@gmail.com \
    --to=raj.khem@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.