From: Martin Schlemmer <azarah@gentoo.org>
To: Paul de Vrieze <pauldv@gentoo.org>
Cc: Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] NPTL ready yet?
Date: Wed, 29 Oct 2003 19:40:49 +0200 [thread overview]
Message-ID: <1067449249.9405.43.camel@nosferatu.lan> (raw)
In-Reply-To: <200310291356.42374.pauldv@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1874 bytes --]
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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-29 17:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 4:28 [gentoo-dev] NPTL ready yet? Joseph Pingenot
2003-10-27 4:46 ` Adam Porich
2003-10-27 6:35 ` Matthew Kennedy
2003-10-27 12:56 ` Mike Frysinger
2003-10-29 12:16 ` Jason Stubbs
2003-10-29 12:56 ` Paul de Vrieze
2003-10-29 17:40 ` Martin Schlemmer [this message]
2003-10-27 9:13 ` Christophe Vanfleteren
2003-10-27 18:02 ` Martin Schlemmer
2003-10-27 19:30 ` Paul de Vrieze
2003-10-27 21:27 ` Martin Schlemmer
2003-10-29 2:36 ` Joseph Pingenot
2003-10-29 3:23 ` Mike Frysinger
2003-10-29 3:35 ` Joseph Pingenot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1067449249.9405.43.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=pauldv@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox