[OE-core] [RFT] Glibc 2.23 and binutils 2.26

Richard Purdie richard.purdie at linuxfoundation.org
Mon Feb 1 09:12:35 UTC 2016


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 at 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





More information about the Openembedded-core mailing list