From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: [meta-raspberrypi] Nothing RPROVIDES 'liborc-0.4'
Date: Wed, 11 Jun 2014 12:28:24 -0600 [thread overview]
Message-ID: <53989FC8.7080905@mlbassoc.com> (raw)
In-Reply-To: <CACwkBCTTVA7YCaxZ7UdTB6dDEjr+96PCzYsSHkJ+k-QC7MvMPw@mail.gmail.com>
On 2014-06-11 12:17, Lukáš Novotný wrote:
> Hello everyone,
>
> I'm trying to build raspberry pi image that includes gstreamer1.0 and
> it's plugins. Packages built successfully, however when trying to
> build the image itself I get error:
>
> Nothing RPROVIDES 'liborc-0.4' (but
> /home/lukas/opt/yocto-daisy/poky/build-raspberrypi/recipes/images/rpi-retail-player-edited-20140611-195509.bb
> RDEPENDS on or otherwise requires it)
>
> Full output when using bitbake directly: http://pastebin.com/2mcUwzAm
>
> Searching for "liborc*" within tmp/deploy returns:
>
> ./rpm/armv6_vfp/liborc-test-0.4-0-0.4.18-r2.0.armv6_vfp.rpm
> ./rpm/armv6_vfp/liborc-0.4-0-0.4.18-r2.0.armv6_vfp.rpm
>
> I have tried also building from 'master' branch of both poky and
> meta-raspberrypi and I'm getting the same error. Any idea on what's
> going on and how to fix it?
What layer are these recipes (liborc, rpi-retail-player-edited)
coming from?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-06-11 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 18:17 [meta-raspberrypi] Nothing RPROVIDES 'liborc-0.4' Lukáš Novotný
2014-06-11 18:28 ` Gary Thomas [this message]
2014-06-11 18:46 ` Lukáš Novotný
2014-06-11 18:57 ` Andrei Gherzan
2014-06-11 20:44 ` Alex J Lennon
2014-06-11 21:43 ` Lukáš Novotný
-- strict thread matches above, loose matches on Subject: below --
2015-02-04 11:58 Gary Pollington
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=53989FC8.7080905@mlbassoc.com \
--to=gary@mlbassoc.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.