Re: [RFT] Moving on from eglibc to glibc 2.20

[Khem Raj <raj.khem@gmail.com>]

On 14-08-28 08:18:57, Richard Purdie wrote:
> On Wed, 2014-08-27 at 23:41 -0700, Khem Raj wrote:
> > Hi All
> > 
> > As we all know eglibc has been merged back into glibc and 2.19 was the
> > last release, here I have put together the recipes for upcoming glibc
> > 2.20 release and removed eglibc 2.19 in favor of move.
> > 
> > I also thought about leaving eglibc in there but then eglibc and glibc
> > were pretty much same as they always have been that it would be an
> > incremental change with lot more patches this time.
> > 
> > The tree is here
> > 
> > http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-to-glibc-2.20
> > 
> > This has not recieved much testing yet and I am looking out for helping
> > hands here, so try it out in your buid environments and machines of
> > interest and report back on issues.
> > 
> > The patches also forward port the options group support and few other
> > patches from eglibc, details are in commit logs, which I think would make 
> > good candidates for future glibc merge.
> > 
> > This tree will be reworked and rebased so sync back if you see issues
> > which we will address here
> > 
> > Thanks for your help
> 
> Thanks for doing this Khem, its quite some work and much appreciated!
> 
> Just to be clear, what is the intent here? Is it intended to get this
> into 1.7 or is this 1.8 material at this point? We're effectively past
> the toolchain freeze point for 1.7, just about at complete feature
> freeze but I'd like to make sure we're thinking the same things.

I am targetting for 1.7 thats why call for wider testing to expedite.  but it could only be decided with some level of
testing. I havent done enough of testing yet myself it to be sure but in coming few days, it
will be lot clear

But if it turns into major issues then we can wait for 1.8 but it will
be quite an effort to keep up with these patches over a long period of time.

> 
> I'm certainly happy to get this through the autobuilder and see what
> happens...
> 

yes, ceertainly would help. 

> Cheers,
> 
> Richard
>