Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>,
	Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFT] Glibc 2.23 and binutils 2.26
Date: Mon, 01 Feb 2016 09:12:35 +0000	[thread overview]
Message-ID: <1454317955.27087.33.camel@linuxfoundation.org> (raw)
In-Reply-To: <1454229127.27087.11.camel@linuxfoundation.org>

On Sun, 2016-01-31 at 08:32 +0000, Richard Purdie wrote:
> On Fri, 2016-01-29 at 06:44 -0800, Khem Raj wrote:
> > On Fri, Jan 29, 2016 at 6:14 AM, Alexander Kanavin
> > <alexander.kanavin@linux.intel.com> wrote:
> > > On 01/17/2016 01:54 PM, Khem Raj wrote:
> > > > 
> > > > upstream glibc and binutils release branches have been cut out
> > > > and are
> > > > being made ready for next release
> > > > I have put together update patchset for both of them
> > > > 
> > > > here are the branches
> > > > 
> > > > https://github.com/kraj/openembedded-core/tree/kraj/binutils-2.
> > > > 26
> > > > https://github.com/kraj/openembedded-core/tree/kraj/glibc-2.23
> > > 
> > > 
> > > Hello Khem,
> > > 
> > > when are you planning to submit these?
> > 
> > binutils exposes a problem for ppc as a result kernel fails to
> > build.
> > The fix is to drop
> > http://git.openembedded.org/openembedded-core/tree/meta/recipes-dev
> > to
> > ols/gcc/gcc-5.3/0030-Enable-SPE-AltiVec-generation-on-powepc-linux
> > -target.patch
> > 
> > that patch makes generic ppc configs to be specific to fsl ppc.
> > but we need context as to why this was done
> > 
> > glibc is still not released.
> 
> I ran the binutils upgrade in -next on the autobuilder. It looked
> mostly good but with poky-lsb we did see:
> 
> https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb
> /b
> uilds/635/steps/BuildImages/logs/stdio
> 
> https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb
> /b
> uilds/635/steps/BuildImages_1/logs/stdio

Good news is I fixed the binutils build issues. 

There was a window of available time on the autobuilder so I tested
glibc 2.23 which failed in ltp with:

https://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/634/steps/BuildImages/logs/stdio

bdflush01.c:84:25: fatal error: sys/kdaemon.h: No such file or directory

That made the builds rather red with many failures but was the only
error I could spot.

Cheers,

Richard




  parent reply	other threads:[~2016-02-01  9:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-17 11:54 [RFT] Glibc 2.23 and binutils 2.26 Khem Raj
2016-01-22  1:28 ` [oe] " akuster808
2016-01-27  2:11 ` ChenQi
2016-01-27  5:30   ` Khem Raj
2016-01-29 14:14 ` Alexander Kanavin
2016-01-29 14:44   ` Khem Raj
2016-01-31  8:32     ` Richard Purdie
2016-01-31  8:53       ` Khem Raj
2016-02-01  9:12       ` Richard Purdie [this message]
2016-02-01 17:02         ` 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=1454317955.27087.33.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alexander.kanavin@linux.intel.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