From: Khem Raj <raj.khem@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
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: [OE-core] [RFT] eglibc 2.19
Date: Wed, 12 Feb 2014 21:45:39 -0800 [thread overview]
Message-ID: <9BE5B941-F71B-444F-84A3-07EF3CA6F9E5@gmail.com> (raw)
In-Reply-To: <81756FDA-0EA9-4393-A4F2-0004E8377A7F@gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Khem Raj <raj.khem@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
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: [RFT] eglibc 2.19
Date: Wed, 12 Feb 2014 21:45:39 -0800 [thread overview]
Message-ID: <9BE5B941-F71B-444F-84A3-07EF3CA6F9E5@gmail.com> (raw)
In-Reply-To: <81756FDA-0EA9-4393-A4F2-0004E8377A7F@gmail.com>
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
next prev parent reply other threads:[~2014-02-13 5:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 16:08 [RFT] eglibc 2.19 Khem Raj
2014-02-10 5:32 ` [OE-core] " Nathan Rossi
2014-02-10 5:32 ` Nathan Rossi
2014-02-10 7:31 ` [OE-core] " Khem Raj
2014-02-10 7:31 ` Khem Raj
2014-02-12 15:41 ` [OE-core] " Richard Purdie
2014-02-12 15:41 ` Richard Purdie
2014-02-12 16:53 ` [OE-core] " Richard Purdie
2014-02-12 16:53 ` Richard Purdie
2014-02-12 17:14 ` [OE-core] " Khem Raj
2014-02-12 17:14 ` Khem Raj
2014-02-12 18:20 ` [OE-core] " Khem Raj
2014-02-12 18:20 ` Khem Raj
2014-02-13 5:45 ` Khem Raj [this message]
2014-02-13 5:45 ` Khem Raj
2014-02-17 15:25 ` [OE-core] " Richard Purdie
2014-02-17 15:25 ` Richard Purdie
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=9BE5B941-F71B-444F-84A3-07EF3CA6F9E5@gmail.com \
--to=raj.khem@gmail.com \
--cc=Openembedded-devel@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.