From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Why is glibc ntpl+nptl-only?
Date: Sat, 16 Sep 2006 09:49:32 +0100 [thread overview]
Message-ID: <200609160949.45886.michaelkintzios@gmail.com> (raw)
In-Reply-To: <200609161014.23081.exzombie@exzombie.homeip.net>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
On Saturday 16 September 2006 09:14, Jure Varlec wrote:
> Well, the new glibc-2.4 only supports nptl, unlike glibc-2.3 which
> supported both threading models. So if you want legacy linuxthreads, you
> have to stay with glibc-2.3.
> As for being "better", glibc-2.4 is better than 2.3 IMHO.
> Also, "nptl -nptlonly" combination with 2.3 actually builds two versions of
> glibc, one with nptl and one with linuxthreads, so you get a longer compile
> and larger disk footprint.
Is there a need for either nptl or nptlonly in our USE flags now that we have
moved over to glibc-2.4 (assuming that we do not want linuxthreads anymore)?
I currently have nptlonly in my make.conf and was wondering whether I should
remove it.
--
Regards,
Mick
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-09-16 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 5:07 [gentoo-user] Why is glibc ntpl+nptl-only? Wolfgang Liebich
2006-09-16 8:14 ` Jure Varlec
2006-09-16 8:49 ` Mick [this message]
2006-09-16 12:59 ` Jan-Hendrik Zab
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=200609160949.45886.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.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