From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org,
openembedded-devel@lists.openembedded.org
Subject: Re: State of bitbake world, Failed tasks 2014-01-03
Date: Sun, 12 Jan 2014 18:35:15 +0100 [thread overview]
Message-ID: <20140112173515.GG16995@jama> (raw)
In-Reply-To: <20140103104408.GC3707@jama>
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
On Fri, Jan 03, 2014 at 11:44:08AM +0100, Martin Jansa wrote:
> With git branches and breakage from freetype upgrade fixed we're back to more
> common list of issues.
>
> webkit-efl is broken because of freetype upgrade, I'm working on efl upgrade to 1.8.*
> so I'll probably fix it later together with efl upgrade.
It fails even with newer webkit-efl, because it's actually broken in
cmake since freetype upgrade in oe-core, fix sent:
http://lists.openembedded.org/pipermail/openembedded-core/2014-January/088218.html
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2014-01-12 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 10:44 State of bitbake world, Failed tasks 2014-01-03 Martin Jansa
2014-01-12 17:35 ` 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=20140112173515.GG16995@jama \
--to=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