| 1 |
On Sat, Jun 02, 2012 at 10:52:12PM -0400, Michael Mol wrote: |
| 2 |
> On Sat, Apr 28, 2012 at 11:07 AM, Michael Mol <mikemol@×××××.com> wrote: |
| 3 |
> Wow. Just wow. This is incredible. |
| 4 |
> |
| 5 |
> This is repeatable for me. |
| 6 |
> |
| 7 |
<snip> |
| 8 |
> * The problem occurred while executing the ebuild file named |
| 9 |
> * 'glibc-2.14.1-r3.ebuild' located in the '/var/db/pkg/sys- |
| 10 |
> |
| 11 |
<snip> |
| 12 |
> CFLAGS="-O2 -pipe -D_FORTIFY_SOURCE=2 -march=core2 -mcx16 -msahf |
| 13 |
> --param l1-cache-size=32 --param l1-cache-line-size=64 --param |
| 14 |
> l2-cache-size=4096 -mtune=core2 -ggdb3" |
| 15 |
> CXXFLAGS="${CFLAGS}" |
| 16 |
|
| 17 |
Can you upgrage to glibc-2.15? |
| 18 |
Can you tweak you gcc flags to something more conventional and see if the |
| 19 |
problem persists? |
| 20 |
If you are interested in submitting a patch to the upstream then you can build |
| 21 |
the glibc test suite with your gcc flags and check if the tests pass. |
| 22 |
|
| 23 |
regards, Dmitry |
Archives