| 1 |
On Mon, May 28, 2007 at 04:01:15PM +0200, Davide Cittaro wrote: |
| 2 |
> Hi all, I've found that glibc 2.5+ cannot be compiled on my alpha, as |
| 3 |
> reported on gentoo bugzilla by another person. |
| 4 |
> |
| 5 |
> http://bugs.gentoo.org/show_bug.cgi?id=179353 |
| 6 |
> |
| 7 |
> I have a couple of questions, then: |
| 8 |
> 1- it is safe to use '-nptlonly' flag? |
| 9 |
Not really. In the past we've found Linuxthreads to be unstable and |
| 10 |
nptlonly is much preferred for that reason (we had programs randomly |
| 11 |
crashing with Linuxthreads and no problems with NPTL). |
| 12 |
|
| 13 |
> 2- when the patched glibc will be available in portage (comment 2 of |
| 14 |
> that bug has been posted one week ago)? |
| 15 |
As soon as glibc upstream fixes the problem. Meanwhile you have two |
| 16 |
different options. |
| 17 |
|
| 18 |
1. Upgrade to binutils >=2.17.50.0.15 and risk possible unknown bugs |
| 19 |
from doing so. |
| 20 |
2. Ignoring glibc-2.5 updates until upstream fixes the issue. |
| 21 |
|
| 22 |
My recommendation would be to wait and not try to work around the issue |
| 23 |
yourself. |
| 24 |
|
| 25 |
Regards, |
| 26 |
Bryan Østergaard |
| 27 |
-- |
| 28 |
gentoo-alpha@g.o mailing list |
Archives