Date: Fri, 26 Mar 2004 01:06:03 -0500 (EST) From: Daniel Eischen <eischen@vigrid.com> To: Kris Kennaway <kris@obsecurity.org> Cc: FreeBSD current users <current@freebsd.org> Subject: Re: SF Bay area hackfest Message-ID: <Pine.GSO.4.10.10403260101140.13825-100000@pcnet5.pcnet.com> In-Reply-To: <20040325074824.GB63710@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 24 Mar 2004, Kris Kennaway wrote: > On Thu, Mar 25, 2004 at 01:22:22AM -0500, Daniel Eischen wrote: > > > We've said this at other times, but TLS support is already > > partially designed in to libpthread (for all archs). We > > can (and will) implement it for them regardless of whether > > the library functions perfectly for those platforms. > > > > Both sparc64 and alpha seem to work OK when libpthread is > > built in 1:1 mode, so I suspect the real problem is resuming > > the thread contexts in userland and/or passing out the > > context in the expected format from the kernel. > > Can it be built that way by default on sparc, since libthr doesn't > work very well? I'd like to test this for things like mozilla that > cause libthr to crash at startup, except my sparc machine remains > unbootable because of broken syscons. Try adding -DSYSTEM_SCOPE_ONLY to CFLAGS when building libpthread, then try it and let me know how it works. libpthread is still built and installed as libkse on sparc64 (and alpha), so you'll also need to libmap libc_r to libkse. -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10403260101140.13825-100000>