Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org,
	openembedded-devel@lists.openembedded.org
Subject: State of bitbake world, Failed tasks 2014-06-02
Date: Mon, 2 Jun 2014 10:49:50 +0200	[thread overview]
Message-ID: <20140602084950.GL2426@jama> (raw)

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

This build still contains huge patch setting B = S or inherit for
autotools-brokensep for all recipes which were failing in earlier
master builds.

abiword and few other recipes issues are now hidden by libgsf failure
most efl recipes are hidden by efl failure (testing 1.10.0 version which I haven't sent to ML yet)
qt5 is broken because it's testing new 5.3.0
firefox broken probably by freetype upgrade

grub.do_package failing again for some reason

http://www.openembedded.org/wiki/Bitbake_World_Status

== Failed tasks 2014-06-02 ==

=== common (9) ===
    * meta-openembedded/meta-gnome/recipes-gnome/libgsf/libgsf_1.14.26.bb, do_compile
    * meta-openembedded/meta-networking/recipes-support/curlpp/curlpp_0.7.3.bb, do_compile
    * meta-openembedded/meta-oe/recipes-navigation/omgps/omgps_svn.bb, do_compile
    * meta-openembedded/meta-oe/recipes-support/eject/eject_2.1.5.bb, do_compile
    * meta-openembedded/meta-xfce/recipes-apps/xfce4-notifyd/xfce4-notifyd_0.2.2.bb, do_compile
    * meta-openembedded/meta-xfce/recipes-apps/xfce4-screenshooter/xfce4-screenshooter_1.8.1.bb, do_compile
    * meta-qt5/recipes-qt/qt5/qtbase_5.3.0.bb, do_compile
    * meta-qt5/recipes-qt/qt5/qtwayland-native_git.bb, do_fetch
    * meta-qt5/recipes-qt/qt5/qtwayland_git.bb, do_fetch

=== common-x86 (3) ===
    * meta-browser/recipes-browser/chromium/chromium_35.0.1883.0.bb, do_compile
    * meta-browser/recipes-mozilla/firefox/firefox_10.0.11esr.bb, do_compile
    * openembedded-core/meta/recipes-bsp/grub/grub_2.00.bb, do_package

=== qemuarm (1) ===
    * meta-openembedded/meta-efl/recipes-efl/efl/efl_1.10.0.bb, do_compile

=== qemux86 (1) ===
    * meta-openembedded/meta-efl/recipes-efl/efl/efl_1.10.0.bb, do_install

=== qemux86_64 (1) ===
    * meta-openembedded/meta-oe/recipes-benchmark/libhugetlbfs/libhugetlbfs_git.bb, do_compile

=== Number of failed tasks ===
{| class=wikitable
|-
||qemuarm       ||10    ||http://logs.nslu2-linux.org/buildlogs/oe/oe-shr-core-branches//log.world.20140530_174007.log/
|-
||qemux86       ||13    ||http://logs.nslu2-linux.org/buildlogs/oe/oe-shr-core-branches//log.world.20140531_061843.log/
|-
||qemux86_64    ||14    ||http://logs.nslu2-linux.org/buildlogs/oe/oe-shr-core-branches//log.world.20140531_204145.log/
|}

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

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

             reply	other threads:[~2014-06-02  8:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02  8:49 Martin Jansa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-06-10 10:07 State of bitbake world, Failed tasks 2014-06-02 Martin Jansa
2014-06-10 11:40 ` Martin Jansa
2014-06-12 11:06   ` Richard Purdie
2014-06-10 15:40 ` akuster@mvista

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=20140602084950.GL2426@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