| 1 |
On Fri, 2005-09-16 at 09:42 -0400, solar wrote: |
| 2 |
> On Fri, 2005-09-16 at 08:35 -0400, Chris Gianelloni wrote: |
| 3 |
> > So... What do we say to going nptl across the board for 2006.0 on every |
| 4 |
> > platform that supports 2.6 headers? This would, of course, require |
| 5 |
> > approval from each arch team, but I'm sure ppc and amd64 are chomping at |
| 6 |
> > the bits for this one, and it sounds like the x86 arch team is wanting |
| 7 |
> > it also. |
| 8 |
> |
| 9 |
> ppc32 - has problems with nptl when not using linuxthreads (oddly it |
| 10 |
> works with ASLR in place however). |
| 11 |
> |
| 12 |
> x86 - sometimes has problems with *some* clients and the RTLD. |
| 13 |
> Seems to be a problem with ld.so paths and having intermixed |
| 14 |
> nptl/shared/static handling but I'm not sure. I have had nothing but |
| 15 |
> success on x86 with it, but others seem to. |
| 16 |
> |
| 17 |
> amd64 - Seems to support it well. |
| 18 |
> |
| 19 |
> mips, sparc, ia64, m68k, arm - (don't know) |
| 20 |
> |
| 21 |
> Sadly we don't really have any NPTL guru's (know of any?) that are able |
| 22 |
> to quickly fix nptl bugs so they just keep piling up in bugzilla. |
| 23 |
> |
| 24 |
> There remain outstanding bugs with nptl problems. |
| 25 |
> |
| 26 |
> http://bugs.gentoo.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&field0-0-0=product&type0-0-0=substring&value0-0-0=nptl&field0-0-1=component&type0-0-1=substring&value0-0-1=nptl&field0-0-2=short_desc&type0-0-2=substring&value0-0-2=nptl&field0-0-3=status_whiteboard&type0-0-3=substring&value0-0-3=nptl |
| 27 |
> |
| 28 |
> uclibc-* does not support nptl yet. |
| 29 |
> |
| 30 |
> To me it would seem the ideal time to make the switch to NPTL is when |
| 31 |
> the toolchain is gcc-4.x/glibc-2.3.6 are doing it by default and in |
| 32 |
> stable. |
| 33 |
|
| 34 |
This actually stems from a discussion on #gentoo-x86 where Azarah was |
| 35 |
discussing how we need to switch to nptl for default specifically for |
| 36 |
gcc-4.x/glibc-2.3.6 to be able to go stable. I'm just trying to get a |
| 37 |
conversation going here on what pitfalls we might run across on various |
| 38 |
platforms and if we're ready to make that plunge. |
| 39 |
|
| 40 |
-- |
| 41 |
Chris Gianelloni |
| 42 |
Release Engineering - Strategic Lead |
| 43 |
Games - Developer |
| 44 |
Gentoo Linux |
Archives