Date: Mon, 14 Jul 2003 08:51:46 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: Kai Mosebach <kai.mosebach@freshx.de> Cc: freebsd-threads@freebsd.org Subject: Re: AW: getpwnam + getpwnam_r + LinuxThreads port = deadlock Message-ID: <Pine.GSO.4.10.10307140841530.19808-100000@pcnet5.pcnet.com> In-Reply-To: <000601c349f9$39b69fe0$0100000a@alpha>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 14 Jul 2003, Kai Mosebach wrote: > > On Sat, 12 Jul 2003, Joshua Oreman wrote: > > > > > > > > > > 3) CVSup to the latest 5.x and use libthr or libkse and > > > > forget linuxthreads. > > > > > I am having the same problems in my sapdb port, as mentioned in another > mail. For me its also not this simple to simply switch to kse, because > then > other kse related problems occur. Like what? The -threads list is a good place to post these problems. > Wouldnt it be more "clean", to fix the issue in the linuxthreads > implementation instead ? (For example many users might use linuxthreads > for mysql compilation for example, not knowing what they await ...) Have you tried sending the problem to the maintainer? Our main concern is libthr and libkse stability for 5.2-release. Eventually the ports system will learn about our other thread libraries and will allow their use in preference to linuxthreads. -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10307140841530.19808-100000>