Re: [gentoo-user] Just a heads-up, I think =sys-libs/glibc-2.14.1-r3 is a stinker.

[Michael Mol <mikemol@gmail.com>]

On Sat, Jun 23, 2012 at 12:37 AM, Michael Mol <mikemol@gmail.com> wrote:
> On Sat, Jun 2, 2012 at 11:56 PM, Michael Mol <mikemol@gmail.com> wrote:
>> On Sat, Jun 2, 2012 at 11:34 PM, Dmitry Goncharov
>> <dgoncharov@users.sf.net> wrote:
>>> On Sat, Jun 02, 2012 at 10:52:12PM -0400, Michael Mol wrote:
>>>> On Sat, Apr 28, 2012 at 11:07 AM, Michael Mol <mikemol@gmail.com> wrote:
>>>> Wow. Just wow. This is incredible.
>>>>
>>>> This is repeatable for me.
>>>>
>>> <snip>
>>>>  * The problem occurred while executing the ebuild file named
>>>>  * 'glibc-2.14.1-r3.ebuild' located in the '/var/db/pkg/sys-
>>>>
>>> <snip>
>>>> CFLAGS="-O2 -pipe -D_FORTIFY_SOURCE=2 -march=core2 -mcx16 -msahf
>>>> --param l1-cache-size=32 --param l1-cache-line-size=64 --param
>>>> l2-cache-size=4096 -mtune=core2 -ggdb3"
>>>> CXXFLAGS="${CFLAGS}"
>>>
>>> Can you upgrage to glibc-2.15?
>>
>> Sure. It's going to be another full reinstall.
>
> Forgot to try this. Will do tomorrow.
>
>>
>>> Can you tweak you gcc flags to something more conventional and see if the
>>> problem persists?
>>
>> Those CFLAGS should be equivalent to:
>> CFLAGS="-O2 -pipe -ggdb3 --march=native".
>>
>> But I'll try making it just -O2 -pipe --march=native.
>
> Just an update: Tried CFLAGS="-O2 -pipe --march=native -ggdb3". Same results.
>
>>
>>> If you are interested in submitting a patch to the upstream then you can build
>>> the glibc test suite with your gcc flags and check if the tests pass.
>
> I do still have a working gentoo laptop I could try this on...but it
> has an i3 proc, as opposed to the core 2 xeon or the phenom 9650. Have
> a link to instructions?

For anyone following or interested, this is now reported as bug
#423149. I'll be tracking progress there, so I have a common place to
keep notes and discoveries as I try to work it out.

https://bugs.gentoo.org/show_bug.cgi?id=423149

-- 
:wq