From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-devel@lists.openembedded.org,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe] State of bitbake world, Failed tasks 2015-06-19
Date: Mon, 22 Jun 2015 15:22:36 +0300 [thread overview]
Message-ID: <5587FE0C.5040705@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZBZJdUbqPWNDsJ6SmgPHmpio0JwVE=xfsen-2OoB0RnQ@mail.gmail.com>
On 06/22/2015 02:07 PM, Burton, Ross wrote:
> I've just filed a bug for this chunk, looks like we missed something when
> disabling GStreamer 0.10 in Qt.
Not really; the recipes for qt-mobility were moved from oe-core to
meta-oe as they were, without any modifications.
This looks like a simple missing dependency issue, but I don't know why
it wasn't reported earlier. Note that there are also missing
dependencies for libxv and qt-creator, so it's not gstreamer-specific
Alex
prev parent reply other threads:[~2015-06-22 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 16:52 State of bitbake world, Failed tasks 2015-06-19 Martin Jansa
2015-06-22 11:07 ` [oe] " Burton, Ross
2015-06-22 12:22 ` Alexander Kanavin [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=5587FE0C.5040705@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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