Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Martin Jansa <martin.jansa@gmail.com>,
	<openembedded-core@lists.openembedded.org>,
	<openembedded-devel@lists.openembedded.org>
Subject: Re: State of bitbake world, Failed tasks 2016-03-09
Date: Fri, 11 Mar 2016 09:41:37 -0600	[thread overview]
Message-ID: <56E2E731.1040005@windriver.com> (raw)
In-Reply-To: <20160310115301.GC2573@jama>

On 3/10/16 5:53 AM, Martin Jansa wrote:
> Aggressive PNBLACKLISTing continues. But linux-yocto (and modules depending on it)
> are still broken :/.
> 
> I'll look at cef3 and chromium issue, my recent patch for meta-browser
> fixed the build for armv7a MACHINEs, so it probably needs to be extended
> a bit to cover warnings in x86 and then duplicate the same to cef3.
> This issue is there for so long, slowing down the builds significantly
> (and causing logs to be much bigger) - I don't use these recipes but I
> hate the failures even more.
> 

Is see the reported log failure, but I've been building with the oe-core and
poky linux-yocto head of master for the last couple weeks, all arches includes
qemux86.

I don't see the error on my builder.  Is something changing the default
recipe/kernel configuration triggering the fault?

--Mark

> === qemux86 (2) ===
>     * /meta-openembedded/meta-python/recipes-devtools/python/python-m2crypto_0.23.0.bb, do_compile
>     * /openembedded-core/meta/recipes-kernel/linux/linux-yocto_4.4.bb, do_compile




  parent reply	other threads:[~2016-03-11 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10 11:53 State of bitbake world, Failed tasks 2016-03-09 Martin Jansa
2016-03-11 15:03 ` Trevor Woerner
2016-03-11 15:41 ` Mark Hatle [this message]
2016-03-11 15:52   ` Bruce Ashfield
2016-03-11 16:13     ` Martin Jansa
2016-03-11 16:21       ` Bruce Ashfield

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=56E2E731.1040005@windriver.com \
    --to=mark.hatle@windriver.com \
    --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