[RFT] eglibc 2.19

[RFT] eglibc 2.19

[Khem Raj]

Hi all

I have staged a branch with eglibc 2.19 upgraded recipes here

http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-2.19

These are not final recipes there may be tweaks needed like adjusting SRC_URI
later on.

please help testing it out in your environments and machines
I would be happy to help out with issues we find

Thank you

-Khem

Re: [RFT] eglibc 2.19

[Nathan Rossi]

> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Khem Raj
> Sent: Sunday, February 09, 2014 2:08 AM
> To: Patches and discussions about the oe-core layer; openembeded-devel;
> yocto@yoctoproject.org
> Subject: [OE-core] [RFT] eglibc 2.19
> 
> Hi all
> 
> I have staged a branch with eglibc 2.19 upgraded recipes here
> 
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-
> 2.19
> 
> These are not final recipes there may be tweaks needed like adjusting
> SRC_URI
> later on.
> 
> please help testing it out in your environments and machines
> I would be happy to help out with issues we find

Hi Khem,

I have given it a test with the machines on the meta-xilinx layer, specifically ARM Cortex A9 and MicroBlaze architectures. And there appears to be no issues.

Also I couldn't access your eglibc source tarball because of pesky corporate web filters, so I used a direct svn export of the upstream repo at the revision 25243, I assume there should be no differences?

On a side note, I haven't seen any mention of what is next regarding oe-core and eglibc. Since the eglibc project has closed its development (http://www.eglibc.org/archives/patches/msg01327.html), and that 2.19 is the final version. Are there any plans to switch oe-core to using glibc for the future? Just curious is all.

Regards,
Nathan

> 
> Thank you
> 
> -Khem
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [RFT] eglibc 2.19

[Khem Raj]

On Sun, Feb 9, 2014 at 9:32 PM, Nathan Rossi <nathan.rossi@xilinx.com> wrote:
>> -----Original Message-----
>> From: openembedded-core-bounces@lists.openembedded.org
>> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
>> Khem Raj
>> Sent: Sunday, February 09, 2014 2:08 AM
>> To: Patches and discussions about the oe-core layer; openembeded-devel;
>> yocto@yoctoproject.org
>> Subject: [OE-core] [RFT] eglibc 2.19
>>
>> Hi all
>>
>> I have staged a branch with eglibc 2.19 upgraded recipes here
>>
>> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-
>> 2.19
>>
>> These are not final recipes there may be tweaks needed like adjusting
>> SRC_URI
>> later on.
>>
>> please help testing it out in your environments and machines
>> I would be happy to help out with issues we find
>
> Hi Khem,
>
> I have given it a test with the machines on the meta-xilinx layer, specifically ARM Cortex A9 and MicroBlaze architectures. And there appears to be no issues.

Thanks for the report.

>
> Also I couldn't access your eglibc source tarball because of pesky corporate web filters, so I used a direct svn export of the upstream repo at the revision 25243, I assume there should be no differences?

there are no functional differences.

>
> On a side note, I haven't seen any mention of what is next regarding oe-core and eglibc. Since the eglibc project has closed its development (http://www.eglibc.org/archives/patches/msg01327.html), and that 2.19 is the final version. Are there any plans to switch oe-core to using glibc for the future? Just curious is all.

Sure there definitely are and we discussed it in Last OE meeting on
IRC recently, we will plan moving to using glibc after 2.19, so these
will be last 2.19 eglibc recipes.

>
> Regards,
> Nathan
>
>>
>> Thank you
>>
>> -Khem
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>

Re: [RFT] eglibc 2.19

[Richard Purdie]

On Sat, 2014-02-08 at 08:08 -0800, Khem Raj wrote:
> Hi all
> 
> I have staged a branch with eglibc 2.19 upgraded recipes here
> 
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-2.19
> 
> These are not final recipes there may be tweaks needed like adjusting SRC_URI
> later on.
> 
> please help testing it out in your environments and machines
> I would be happy to help out with issues we find

The autobuilder is still going but it found:

http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/25/steps/BuildImages/logs/stdio

so far.

Cheers,

Richard

Re: [RFT] eglibc 2.19

[Richard Purdie]

On Wed, 2014-02-12 at 15:41 +0000, Richard Purdie wrote:
> On Sat, 2014-02-08 at 08:08 -0800, Khem Raj wrote:
> > Hi all
> > 
> > I have staged a branch with eglibc 2.19 upgraded recipes here
> > 
> > http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-2.19
> > 
> > These are not final recipes there may be tweaks needed like adjusting SRC_URI
> > later on.
> > 
> > please help testing it out in your environments and machines
> > I would be happy to help out with issues we find
> 
> The autobuilder is still going but it found:
> 
> http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/25/steps/BuildImages/logs/stdio

the valgrind configure check breaks too:

http://autobuilder.yoctoproject.org/main/builders/minnow/builds/25/steps/BuildImages/logs/stdio

Cheers,

Richard

Re: [RFT] eglibc 2.19

[Khem Raj]

On Feb 12, 2014, at 8:53 AM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:

> On Wed, 2014-02-12 at 15:41 +0000, Richard Purdie wrote:
>> On Sat, 2014-02-08 at 08:08 -0800, Khem Raj wrote:
>>> Hi all
>>> 
>>> I have staged a branch with eglibc 2.19 upgraded recipes here
>>> 
>>> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-2.19
>>> 
>>> These are not final recipes there may be tweaks needed like adjusting SRC_URI
>>> later on.
>>> 
>>> please help testing it out in your environments and machines
>>> I would be happy to help out with issues we find
>> 
>> The autobuilder is still going but it found:
>> 
>> http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/25/steps/BuildImages/logs/stdio
> 
> the valgrind configure check breaks too:
> 
> http://autobuilder.yoctoproject.org/main/builders/minnow/builds/25/steps/BuildImages/logs/stdio

For this I pushed a fix to pull branch just now.

> 
> Cheers,
> 
> Richard

Re: [RFT] eglibc 2.19

[Khem Raj]

On Feb 12, 2014, at 7:41 AM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:

> On Sat, 2014-02-08 at 08:08 -0800, Khem Raj wrote:
>> Hi all
>> 
>> I have staged a branch with eglibc 2.19 upgraded recipes here
>> 
>> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-2.19
>> 
>> These are not final recipes there may be tweaks needed like adjusting SRC_URI
>> later on.
>> 
>> please help testing it out in your environments and machines
>> I would be happy to help out with issues we find
> 
> The autobuilder is still going but it found:
> 
> http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/25/steps/BuildImages/logs/stdio

I could reproduce it.

This seems to be surfaced by a commit in glibc where the  math_ldbl.h implementations for ppc were unified. I have for now reverted it via patch and pushed to pull branch. however thats not only the one issue :(. I am now seeing

| ../sysdeps/powerpc/fpu/fenv_libc.h:48:6: error: impossible constraint in 'asm'
|       asm volatile ("mtfsf 0xff,%0" : : "f" (d)); \
|       ^



> 
> so far.
> 
> Cheers,
> 
> Richard
> 

Re: [RFT] eglibc 2.19

[Khem Raj]

Hi Richard, All

On Feb 12, 2014, at 10:20 AM, Khem Raj <raj.khem@gmail.com> wrote:

> 
> On Feb 12, 2014, at 7:41 AM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> 
>> On Sat, 2014-02-08 at 08:08 -0800, Khem Raj wrote:
>>> Hi all
>>> 
>>> I have staged a branch with eglibc 2.19 upgraded recipes here
>>> 
>>> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-2.19
>>> 
>>> These are not final recipes there may be tweaks needed like adjusting SRC_URI
>>> later on.
>>> 
>>> please help testing it out in your environments and machines
>>> I would be happy to help out with issues we find
>> 
>> The autobuilder is still going but it found:
>> 
>> http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/25/steps/BuildImages/logs/stdio
> 
> I could reproduce it.
> 
> This seems to be surfaced by a commit in glibc where the  math_ldbl.h implementations for ppc were unified. I have for now reverted it via patch and pushed to pull branch. however thats not only the one issue :(. I am now seeing
> 
> | ../sysdeps/powerpc/fpu/fenv_libc.h:48:6: error: impossible constraint in 'asm'
> |       asm volatile ("mtfsf 0xff,%0" : : "f" (d)); \
> |       ^
> 

Alright, the real problem was that in glibc 2.19 the SPE patch was upsteamed from eglibc and now the SPE support lives under nofpu/ which is correct unlike
eglibc where it was living under fpu/ class. We were not passing —without-fp
to eglibc configure which caused this issue. I have now fixed it in metadata
and pushed a new set of patches ( total 2) to the pull branch, which should take of this issue as well as valgrind issue. 

Thanks
-Khem

Re: [RFT] eglibc 2.19

[Richard Purdie]

On Sat, 2014-02-08 at 08:08 -0800, Khem Raj wrote:
> Hi all
> 
> I have staged a branch with eglibc 2.19 upgraded recipes here
> 
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-2.19
> 
> These are not final recipes there may be tweaks needed like adjusting SRC_URI
> later on.
> 
> please help testing it out in your environments and machines
> I would be happy to help out with issues we find

For what its worth, the last build with the updated patches in passed on
the autobuilder.

Cheers,

Richard