From: Daniel Ostrow <dostrow@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] 2006.0? nptl?
Date: Fri, 16 Sep 2005 10:20:16 -0400 [thread overview]
Message-ID: <1126880416.7832.3.camel@Memoria.anyarch.net> (raw)
In-Reply-To: <1126880197.23324.123.camel@cgianelloni.nuvox.net>
On Fri, 2005-09-16 at 10:16 -0400, Chris Gianelloni wrote:
> On Fri, 2005-09-16 at 09:42 -0400, solar wrote:
> > On Fri, 2005-09-16 at 08:35 -0400, Chris Gianelloni wrote:
> > > So... What do we say to going nptl across the board for 2006.0 on every
> > > platform that supports 2.6 headers? This would, of course, require
> > > approval from each arch team, but I'm sure ppc and amd64 are chomping at
> > > the bits for this one, and it sounds like the x86 arch team is wanting
> > > it also.
> >
> > ppc32 - has problems with nptl when not using linuxthreads (oddly it
> > works with ASLR in place however).
> >
> > x86 - sometimes has problems with *some* clients and the RTLD.
> > Seems to be a problem with ld.so paths and having intermixed
> > nptl/shared/static handling but I'm not sure. I have had nothing but
> > success on x86 with it, but others seem to.
> >
> > amd64 - Seems to support it well.
> >
> > mips, sparc, ia64, m68k, arm - (don't know)
> >
Speaking only for ppc64 we have been running nptl or nptlonly systems
for a good while now and *almost* took the plunge to make it the default
in 2005.1. For us this would be a welcome change.
--
Daniel Ostrow
Gentoo Foundation Board of Trustees
Gentoo/{PPC,PPC64,DevRel}
dostrow@gentoo.org
--
gentoo-releng@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-16 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 12:35 [gentoo-releng] 2006.0? nptl? Chris Gianelloni
2005-09-16 13:42 ` solar
2005-09-16 14:16 ` Chris Gianelloni
2005-09-16 14:20 ` Daniel Ostrow [this message]
2005-09-18 2:47 ` Kumba
2005-09-16 14:18 ` Jason Wever
2005-09-16 14:30 ` Chris Gianelloni
2005-09-17 13:30 ` kloeri
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=1126880416.7832.3.camel@Memoria.anyarch.net \
--to=dostrow@gentoo.org \
--cc=gentoo-releng@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