Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	openembeded-devel <Openembedded-devel@lists.openembedded.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade
Date: Wed, 18 Feb 2015 07:46:15 +0000	[thread overview]
Message-ID: <1424245575.25541.19.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1sofS7MteZnPsTYRNAcMwrrh=T3FP+ASmAOGDMhcwyXB4g@mail.gmail.com>

On Tue, 2015-02-17 at 23:15 -0800, Khem Raj wrote:
> On Sat, Feb 14, 2015 at 2:06 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > Hi Khem,
> >
> > On Thu, 2015-02-12 at 15:35 +0800, Khem Raj wrote:
> >> I have refreshed the branch to include the patch which moves the src
> >> uri to use the newly released glibc 2.21 branch
> >> and please run it via autobuilder ( top 5 commits )
> >
> > Its running on the autobuilder at the moment. Errors will be reported to
> > the error reporting system and can be seen at:
> >
> > http://errors.yoctoproject.org/Errors/Search/?items=10&query=be29d13a847d458efaf542ed302e48050f67a655
> >
> > Right now, poky-tiny failed due to warning are errors and unused
> > symbols. Minnow failed due to SSE instruction issues. Full build logs
> > are also available on the autobuilder:
> >
> > https://autobuilder.yoctoproject.org/main/tgrid
> >
> > as ross/mut-next. We do have other changes in the branch but the above
> > are pretty clearly glibc.
> >
> > Other errors will go to the places above as the builds complete/fail.
> 
> Thanks. So I see following errors categories and status
> 
> 1. valgrind - Martin already sent a patch for that
> 2. slang - I could not yet reproduce it on my active build (mips) (
> seems specific to x86/ppc )
> 3. poky-tiny - glibc build - ( pushed a fix for that in latest pull tree)
> 4. minnow/qemux86 - glibc failure - ( pushed a fix for that in latest
> pull tree )
> 5. glibc build failure on qemuarm - need to reproduce here
> 6. Image failures are probably due to above not building
> 
> I might get slang reproduced soon on qemux86 if I do I will try to
> push for a fix

I think slang is a parallel make race from another patch so don't worry
about that one, Robert will likely get that when he comes back.

Cheers,

Richard



  reply	other threads:[~2015-02-18  7:46 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 10:02 [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade Khem Raj
2015-02-02 10:40 ` [yocto] " Burton, Ross
2015-02-02 10:53   ` Khem Raj
2015-02-02 10:54   ` Khem Raj
2015-02-02 17:25     ` Burton, Ross
2015-02-02 17:40       ` Khem Raj
2015-02-02 17:50         ` Burton, Ross
2015-02-02 18:33           ` Khem Raj
2015-02-02 21:45             ` Burton, Ross
2015-02-03  5:03               ` Khem Raj
2015-02-03 11:55                 ` Burton, Ross
2015-02-03 14:43                 ` Dan McGregor
2015-02-12  7:35                   ` Khem Raj
2015-02-14  7:53                     ` Burton, Ross
2015-02-14 10:06                     ` Richard Purdie
2015-02-14 13:08                       ` Burton, Ross
2015-02-14 15:15                         ` Dan McGregor
2015-02-15 21:59                       ` Richard Purdie
2015-02-17 17:50                         ` Martin Jansa
2015-02-17 19:02                           ` [PATCH 1/2] valgrind: add glibc-2.21 to glibc.patch Martin Jansa
2015-02-17 19:02                             ` [PATCH 2/2] license.bbclass: fix unexpected operator for LICENSE values with space Martin Jansa
2015-02-18  7:15                       ` [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade Khem Raj
2015-02-18  7:46                         ` Richard Purdie [this message]
2015-02-18  9:01                           ` Khem Raj
2015-02-18 11:51                             ` Richard Purdie
2015-02-18 13:06                               ` Richard Purdie
2015-02-18 18:38                                 ` Khem Raj
2015-02-18 21:41                                   ` Richard Purdie
2015-02-19  0:23                                     ` Khem Raj
2015-02-19  0:28                                       ` Khem Raj
2015-02-19  0:31                                         ` Khem Raj
2015-02-19  3:36                                           ` Khem Raj
     [not found] ` <54CFA8A5.7090504@mvista.com>
2015-02-02 17:26   ` Burton, Ross
2015-02-02 17:43     ` Khem Raj
2015-02-20 18:03 ` Richard Purdie
2015-02-21  0:27   ` Peter Urbanec
2015-02-24  6:34     ` Khem Raj
2015-02-21  9:22   ` Richard Purdie
2015-02-24  6:59     ` Khem Raj
2015-02-24 21:58       ` 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=1424245575.25541.19.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Openembedded-devel@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=yocto@yoctoproject.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