Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>,
	openembedded-core@lists.openembedded.org, "Ashfield,
	Bruce" <Bruce.Ashfield@windriver.com>
Subject: Re: [PATCH 4/6] tcmode-default: Bump gcc,glibc,gdb
Date: Sun, 15 May 2016 08:03:44 +0100	[thread overview]
Message-ID: <1463295824.9746.152.camel@linuxfoundation.org> (raw)
In-Reply-To: <2cc568062314cdddd5ff2f60dd6d9685b3b12831.1463157783.git.raj.khem@gmail.com>

On Fri, 2016-05-13 at 09:46 -0700, Khem Raj wrote:
> gcc 6.1, glibc 2.24, gdb 7.11
> 
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
>  meta/conf/distro/include/tcmode-default.inc | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

I'll merge most of this series however before we can move to gcc6 by
default there are some remaining issues:

https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/b
uilds/788/steps/BuildImages/logs/stdio

qt4-x11-free fails to compile
linux-yocto 4.1 also fails

(on qemux86-64, qemux86, qemuppc, qemumips, qemuarm)

https://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/7
78/steps/BuildImages_1/logs/stdio

linux-yocto 4.4 fails on ppc

https://autobuilder.yoctoproject.org/main/builders/nightly-non-gpl3/bui
lds/768/steps/BuildImages/logs/stdio

non-GPLv3 on elfutils and diffutils

(There may be other failures too, the build hasn't completed yet)

We'll need to come up with a plan to address these issues (possibly
upgrades for some of the kernels?) before we can change the defaults.

Cheers,

Richard




  reply	other threads:[~2016-05-15  7:03 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 [this message]
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
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=1463295824.9746.152.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox