Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
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 12:04:22 +0200	[thread overview]
Message-ID: <20140624100422.GM2437@jama> (raw)
In-Reply-To: <1403600852.2104.125.camel@ted>

[-- Attachment #1: Type: text/plain, Size: 1682 bytes --]

On Tue, Jun 24, 2014 at 10:07:32AM +0100, Richard Purdie wrote:
> 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 :/.

This is caused by newer libav-9*, sorry I haven't said that in e-mail (I
did in some previous status updates though).

I've returned PREFERRED_VERSION for libav-9* because there was some talk
about making it default and (re)moving libav-0.8.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

      reply	other threads:[~2014-06-24 10:04 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
2014-06-24 10:04   ` Martin Jansa [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=20140624100422.GM2437@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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