From: Wolfgang Liebich <Wolfgang.Liebich@siemens.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Why is glibc ntpl+nptl-only?
Date: Fri, 15 Sep 2006 07:07:08 +0200 [thread overview]
Message-ID: <20060915050708.GA26894@pce151.ram.siemens.at> (raw)
Hi,
For my new gentoo system I switched to the latest & greatest profile -
2006.1. During the initial installation emerge told me "glibc 2.4 is
nptlonly" - so I turned on the nptl and nptlonly USE flags in make.conf.
Now my old linux system (profile 2006.0) tells me the same.
Sooo - i guess I would have to switch to the no-nptl profile in order to
keep the old (-nptl -nptlonly) settings. Is this a good Idea? Or is
using nptl+nptlonly better (faster, less hassle, less memory footprint)
anyways?
TIA,
Wolfgang Liebich
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2006-09-15 5:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 5:07 Wolfgang Liebich [this message]
2006-09-16 8:14 ` [gentoo-user] Why is glibc ntpl+nptl-only? Jure Varlec
2006-09-16 8:49 ` Mick
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=20060915050708.GA26894@pce151.ram.siemens.at \
--to=wolfgang.liebich@siemens.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