1 |
On Sat, Jun 2, 2012 at 11:34 PM, Dmitry Goncharov |
2 |
<dgoncharov@××××××××.net> wrote: |
3 |
> On Sat, Jun 02, 2012 at 10:52:12PM -0400, Michael Mol wrote: |
4 |
>> On Sat, Apr 28, 2012 at 11:07 AM, Michael Mol <mikemol@×××××.com> wrote: |
5 |
>> Wow. Just wow. This is incredible. |
6 |
>> |
7 |
>> This is repeatable for me. |
8 |
>> |
9 |
> <snip> |
10 |
>> * The problem occurred while executing the ebuild file named |
11 |
>> * 'glibc-2.14.1-r3.ebuild' located in the '/var/db/pkg/sys- |
12 |
>> |
13 |
> <snip> |
14 |
>> CFLAGS="-O2 -pipe -D_FORTIFY_SOURCE=2 -march=core2 -mcx16 -msahf |
15 |
>> --param l1-cache-size=32 --param l1-cache-line-size=64 --param |
16 |
>> l2-cache-size=4096 -mtune=core2 -ggdb3" |
17 |
>> CXXFLAGS="${CFLAGS}" |
18 |
> |
19 |
> Can you upgrage to glibc-2.15? |
20 |
|
21 |
Sure. It's going to be another full reinstall. |
22 |
|
23 |
> Can you tweak you gcc flags to something more conventional and see if the |
24 |
> problem persists? |
25 |
|
26 |
Those CFLAGS should be equivalent to: |
27 |
CFLAGS="-O2 -pipe -ggdb3 --march=native". |
28 |
|
29 |
But I'll try making it just -O2 -pipe --march=native. |
30 |
|
31 |
> If you are interested in submitting a patch to the upstream then you can build |
32 |
> the glibc test suite with your gcc flags and check if the tests pass. |
33 |
|
34 |
If it gets things fixed. I have two machines which have been offline |
35 |
for almost two months from this. |
36 |
|
37 |
-- |
38 |
:wq |