On Wed, 2003-10-29 at 14:56, Paul de Vrieze wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Wednesday 29 October 2003 13:16, Jason Stubbs wrote:
> > I used NPTL for about four weeks and had no problems except that
> > canna, a Japanese input server, would not start. Other than that, I
> > didn't detect any change in the system, performance-wise or otherwise.
> >
> > On Monday 27 October 2003 21:56, Mike Frysinger wrote:
> > > On Monday 27 October 2003 01:35, Matthew Kennedy wrote:
> > > > Whats involved in updating a non-NPTL glibc to NPTL glibc?  Just
> > > > "USE=nptl emerge glibc" or do other libraries and binaries need to
> > > > be re-emerged also?
> > >
> > > no, just re-emerging glibc with nptl in USE is enough
> >
> > As far as I know, only OpenOffice and Sun JRE/JDK have support for
> > NPTL. Wouldn't these need to be re-emerged to take advantage of it?
> 
> I don't know about openoffice remerging. Basically the support consists 
> of making openoffice compile on nptl based systems. An allready compiled 
> openoffice should though run fine with nptl.
> 
> It seems that the same is true for the j2sdk java source package (looking 
> at the patch). It could be however that the headers from the nptl 
> implementation of pthreads allow better optimization, but I don't know. 
> In that case you would need to recompile everything that uses the 
> pthread lib.
> 

AFIAK, you do not need to recompile anything to use it - anything using
libpthread will use it.  You may however have issues recompiling things
as there was some changes, and things heavy dependent on how
linuxthreads worked (valgrind, gdb, etc) may or may not misbehave, but
mostly the rest works just fine.


Thanks,

-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa