| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Wednesday 29 October 2003 13:16, Jason Stubbs wrote: |
| 5 |
> I used NPTL for about four weeks and had no problems except that |
| 6 |
> canna, a Japanese input server, would not start. Other than that, I |
| 7 |
> didn't detect any change in the system, performance-wise or otherwise. |
| 8 |
> |
| 9 |
> On Monday 27 October 2003 21:56, Mike Frysinger wrote: |
| 10 |
> > On Monday 27 October 2003 01:35, Matthew Kennedy wrote: |
| 11 |
> > > Whats involved in updating a non-NPTL glibc to NPTL glibc? Just |
| 12 |
> > > "USE=nptl emerge glibc" or do other libraries and binaries need to |
| 13 |
> > > be re-emerged also? |
| 14 |
> > |
| 15 |
> > no, just re-emerging glibc with nptl in USE is enough |
| 16 |
> |
| 17 |
> As far as I know, only OpenOffice and Sun JRE/JDK have support for |
| 18 |
> NPTL. Wouldn't these need to be re-emerged to take advantage of it? |
| 19 |
|
| 20 |
I don't know about openoffice remerging. Basically the support consists |
| 21 |
of making openoffice compile on nptl based systems. An allready compiled |
| 22 |
openoffice should though run fine with nptl. |
| 23 |
|
| 24 |
It seems that the same is true for the j2sdk java source package (looking |
| 25 |
at the patch). It could be however that the headers from the nptl |
| 26 |
implementation of pthreads allow better optimization, but I don't know. |
| 27 |
In that case you would need to recompile everything that uses the |
| 28 |
pthread lib. |
| 29 |
|
| 30 |
Paul |
| 31 |
|
| 32 |
- -- |
| 33 |
Paul de Vrieze |
| 34 |
Gentoo Developer |
| 35 |
Mail: pauldv@g.o |
| 36 |
Homepage: http://www.devrieze.net |
| 37 |
-----BEGIN PGP SIGNATURE----- |
| 38 |
Version: GnuPG v1.2.3 (GNU/Linux) |
| 39 |
|
| 40 |
iD8DBQE/n7kKbKx5DBjWFdsRAj+cAKDnfUWAkg4MO7YlXAZTRykIrFVMQgCgtu4L |
| 41 |
G8+WWmXeSyd+iIQP0VXSGdo= |
| 42 |
=H/i0 |
| 43 |
-----END PGP SIGNATURE----- |
| 44 |
|
| 45 |
|
| 46 |
-- |
| 47 |
gentoo-dev@g.o mailing list |
Archives