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