From owner-freebsd-threads@FreeBSD.ORG Sun Jun 1 00:43:26 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FACB37B401 for ; Sun, 1 Jun 2003 00:43:26 -0700 (PDT) Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42A5143F85 for ; Sun, 1 Jun 2003 00:43:24 -0700 (PDT) (envelope-from netch@iv.nn.kiev.ua) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id h617hMXM010986; Sun, 1 Jun 2003 10:43:22 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.12.8p1/8.12.8) id h517h7Q9005984; Sun, 1 Jun 2003 10:43:07 +0300 (EEST) (envelope-from netch) Date: Sun, 1 Jun 2003 10:43:07 +0300 From: Valentin Nechayev To: Daniel Eischen Message-ID: <20030601074307.GB5594@iv.nn.kiev.ua> References: <20030531024932.GP61246@over-yonder.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-42: On Organization: Dark side of coredump cc: threads@freebsd.org Subject: Re: Transition plans: libkse->libpthread X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2003 07:43:26 -0000 Sat, May 31, 2003 at 01:39:59, eischen (Daniel Eischen) wrote about "Re: Transition plans: libkse->libpthread": DE> No :-) In my mind, the KSE threads library was always supposed DE> to be libpthread (note the 'p' for POSIX). libthr is not able DE> to be fully POSIX compat because the kernel schedules threads DE> and the kernel doesn't conform to POSIX scheduling. I know I'm DE> in the minority, but I think libthr interfaces should "thr_foo()" DE> (similar to Solaris libthread), not "pthread_foo()". But that DE> prevents it from being easily used as a drop-in replacement DE> for libc_r. Can you link one app both with libthr and libpthread? I think no ;) You can add thr_* as alias or for any function specific to libthr, but there are no direct reason to prohibit libthr having pthread interface. DE> We have a mechanism for selecting the threads library that DE> the ports system should be using (PTHREAD_LIBS); it's just DE> not always being obeyed by some ports. How about customizing -pthread or -lpthread flags on GCC level? (Untested idea) -netch-