From: Herman van Hazendonk <me@herrie.org>
To: Karim ATIKI <karim_atiki@hotmail.com>
Cc: yocto <yocto@yoctoproject.org>
Subject: Re: [meta-raspberrypi3] Failed to build gstreamer1.0-plugins-bad with minimal configuration
Date: Fri, 28 Oct 2016 09:28:57 +0200 [thread overview]
Message-ID: <5ad9653ec6fe57bfd53f9a5413bc359d@herrie.org> (raw)
In-Reply-To: <DB5PR01MB188012CEF43ADE751770A39D92AD0@DB5PR01MB1880.eurprd01.prod.exchangelabs.com>
[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]
Hi Paul/Karim/Khem,
We're using a similar configuration and also facing issues with the
gstreamer1.0-plugins-bad recipe. Though our seems slightly different
(see attached). We did have it working before, but things stopped
working after we moved from Fido through Jethro to Krogoth.
What we're using is: meta-qt5/krogoth, meta-openembedded/krogoth,
openembedded-core/krogoth and some of our own layers
meta-webos-ports/krogoth and meta-rpi-luneos/krogoth.
Not sure it has the same root cause, but I find it interesting it's
failing at the same recipe, so I hope my log might be able to help
resolve this for both of us.
Herman
On 2016-10-28 07:56, Karim ATIKI wrote:
> Hi Paul,
>
> Thanks a lot for your feedback and analysis.
>
> I think it sohuld compile without X11 and Wayland as it's a very
> common configuration
>
> for RaspberryPi being used with Qt5.x applications.
>
> Do you think it's bug related to Gstreamer1.0 configuration ?
>
> Karim
>
> -------------------------
>
> DE : Paul Barker <paul@paulbarker.me.uk>
> ENVOYÉ : jeudi 27 octobre 2016 23:18
> À : Karim ATIKI
> CC : yocto
> OBJET : Re: [yocto] [meta-raspberrypi3] Failed to build
> gstreamer1.0-plugins-bad with minimal configuration
>
> gstreamer1.0-plugins-bad compiles if x11, wayland and opengl are all
> missing from DISTRO_FEATURES. It fails if x11 and wayland are missing
> but opengl is included.
>
> Should it compile if x11 and wayland are removed from DISTRO_FEATURES
> but opengl is included? I don't do much on the graphics side so I
> don't
> know if this makes sense as a configuration.
>
> Thanks,
> Paul
[-- Attachment #2: log.do_compile.zip --]
[-- Type: application/zip, Size: 14146 bytes --]
next prev parent reply other threads:[~2016-10-28 7:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 12:56 [meta-raspberrypi3] Failed to build gstreamer1.0-plugins-bad with minimal configuration Karim ATIKI
2016-10-27 20:26 ` Paul Barker
2016-10-27 21:18 ` Paul Barker
2016-10-28 2:40 ` Khem Raj
2016-10-28 5:56 ` Karim ATIKI
2016-10-28 7:28 ` Herman van Hazendonk [this message]
2016-10-29 21:13 ` Paul Barker
2016-11-01 18:51 ` Karim ATIKI
2016-11-03 2:57 ` Khem Raj
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=5ad9653ec6fe57bfd53f9a5413bc359d@herrie.org \
--to=me@herrie.org \
--cc=karim_atiki@hotmail.com \
--cc=yocto@yoctoproject.org \
--cc=yoctoproject.org@herrie.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.