From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>,
Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/6] tcmode-default: Bump gcc,glibc,gdb
Date: Thu, 26 May 2016 15:15:52 +0100 [thread overview]
Message-ID: <1464272152.19134.33.camel@linuxfoundation.org> (raw)
In-Reply-To: <1464185744.9570.101.camel@linuxfoundation.org>
On Wed, 2016-05-25 at 15:15 +0100, Richard Purdie wrote:
> Just realised the failure is in mpc8315e_rdb so its meta-yocto-bsp
> bumps we're missing?
To update on this, python-pyqt broke once qt4 was building. This was
due to webkit in qt4 being silently disabled. I've merged a patch to
meta-qt4 to handle that and the python-pyqt issue is then fixed.
We were also still having linux-yocto-4.1 issues on meta-yocto-bsp,
which looked like the same problem as we were having with 4.4, a lack
of a SRCREV bump.
Bruce: I took the liberty of testing:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=c87f
66e1b8f4eced3da1b7aaeceb2341674fa61c
which bumps the SRCREVs for 4.1 in meta-yocto-bsp. This is looking
greener on the autobuilder, I'm hoping if this works we could finally
merge gcc6. Can I merge that SRCREV bump?
Sadly all this debugging/testing is holding up the rest of the patch
queue :(.
Cheers,
Richard
next prev parent reply other threads:[~2016-05-26 14:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 16:46 [PATCH 0/6] Glibc/gdb upgrade switch to gcc-6 as default Khem Raj
2016-05-13 16:46 ` [PATCH 1/6] glibc: Add recipes for 2.24 release Khem Raj
2016-07-03 13:45 ` Trevor Woerner
2016-07-03 15:02 ` Khem Raj
2016-07-05 14:56 ` Trevor Woerner
2016-05-13 16:46 ` [PATCH 2/6] python-native: Point to expat in native sysroot and add missing dep on expat-native Khem Raj
2016-05-13 16:46 ` [PATCH 3/6] gdb: Upgrade to 7.11 Khem Raj
2016-05-13 16:46 ` [PATCH 4/6] tcmode-default: Bump gcc,glibc,gdb Khem Raj
2016-05-15 7:03 ` Richard Purdie
2016-05-15 9:25 ` Khem Raj
2016-05-16 12:49 ` Bruce Ashfield
2016-05-16 13:38 ` Bruce Ashfield
2016-05-24 14:51 ` Richard Purdie
2016-05-24 15:51 ` Bruce Ashfield
2016-05-24 18:18 ` Khem Raj
2016-05-25 6:39 ` Richard Purdie
2016-05-25 8:23 ` Khem Raj
2016-05-25 12:03 ` Bruce Ashfield
2016-05-25 12:01 ` Bruce Ashfield
2016-05-25 12:32 ` Bruce Ashfield
2016-05-25 13:31 ` Bruce Ashfield
2016-05-25 13:56 ` Richard Purdie
2016-05-25 14:15 ` Richard Purdie
2016-05-25 14:16 ` Bruce Ashfield
2016-05-26 14:15 ` Richard Purdie [this message]
2016-05-26 14:17 ` Bruce Ashfield
2016-05-13 16:46 ` [PATCH 5/6] linux-yocto/4.4: gcc6 build fixes (powerpc and mips) Khem Raj
2016-05-13 16:46 ` [PATCH 6/6] feature-arm-vfp.inc: fix overzealous ARMPKGSFX_FPU modification Khem Raj
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=1464272152.19134.33.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.