From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Issues building vlc
Date: Tue, 07 Apr 2015 10:00:14 -0400 [thread overview]
Message-ID: <5523E2EE.7020904@balister.org> (raw)
In-Reply-To: <5523E21B.5070100@mlbassoc.com>
On 04/07/2015 09:56 AM, Gary Thomas wrote:
> I'm trying to build vlc and I get this error:
> ERROR: Multiple .bb files are due to be built which each provide jpeg
> (/local/poky-cutting-edge/meta-oe/recipes-core/jpeg/libjpeg-turbo_8d+1.4.0.bb
> /local/poky-cutting-edge/meta/recipes-core/jpeg/jpeg_8d.bb).
> This usually means one provides something the other doesn't and should.
>
> This comes from the fact that vlc depends on libjpeg-turbo
> which conflicts with the main jpeg library in OE-core.
>
> What's the best way to fix this?
This page starts to explain:
http://openembedded.org/wiki/PREFERRED_PROVIDER_for_jpeg_and_jpeg-native
It could use some work explaining the difference between the two
alternatives.
Philip
>
> Thanks
>
next prev parent reply other threads:[~2015-04-07 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 13:56 Issues building vlc Gary Thomas
2015-04-07 14:00 ` Philip Balister [this message]
2015-04-07 17:53 ` Gary Thomas
2015-04-08 21:31 ` 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=5523E2EE.7020904@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox