From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: State of bitbake world, Failed tasks 2014-06-21
Date: Tue, 24 Jun 2014 10:07:32 +0100 [thread overview]
Message-ID: <1403600852.2104.125.camel@ted> (raw)
In-Reply-To: <20140621080922.GE2117@jama>
On Sat, 2014-06-21 at 10:09 +0200, Martin Jansa wrote:
> On Wed, Jun 11, 2014 at 12:57:59PM +0200, Martin Jansa wrote:
> > On Tue, Jun 10, 2014 at 12:07:22PM +0200, Martin Jansa wrote:
> > > On Mon, Jun 02, 2014 at 10:49:50AM +0200, Martin Jansa wrote:
> > > > This build still contains huge patch setting B = S or inherit for
> > > > autotools-brokensep for all recipes which were failing in earlier
> > > > master builds.
> >
> > I've removed this patch for this build to see how bad it is. And it's BAD.
>
> Now it doesn't have the big B=S patch, but long patchset of PNBLACKLISTs I've sent
> earlier this week.
>
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Failed tasks 2014-06-21 ==
>
> I have a fix for python-cython. This doesn't include the big patch from RP.
>
> === common (28) ===
[...]
> * openembedded-core/meta/recipes-multimedia/gstreamer/gst-ffmpeg_0.10.13.bb, do_configure
The gst-ffmpeg failure is somewhat strange. Both libav and libpostproc
can provide libpostproc but at least in my tests, it builds just fine
regardless of which one(s) I've previously built (both in OE-Core and
with meta-oe added).
So I'm not sure why its happening or therefore how to fix it :/.
Cheers,
Richard
next prev parent reply other threads:[~2014-06-24 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-21 8:09 State of bitbake world, Failed tasks 2014-06-21 Martin Jansa
2014-06-24 9:07 ` Richard Purdie [this message]
2014-06-24 10:04 ` Martin Jansa
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=1403600852.2104.125.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=martin.jansa@gmail.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