From owner-freebsd-threads@FreeBSD.ORG Mon Apr 21 14:55:15 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 0E8F537B401 for ; Mon, 21 Apr 2003 14:55:15 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06F6A43FDD for ; Mon, 21 Apr 2003 14:55:14 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (localhost [127.0.0.1]) by haldjas.folklore.ee (8.12.3/8.11.3) with ESMTP id h3LLseUE030825; Tue, 22 Apr 2003 00:54:40 +0300 (EEST) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost)h3LLsdJK030822; Tue, 22 Apr 2003 00:54:39 +0300 (EEST) Date: Tue, 22 Apr 2003 00:54:37 +0300 (EEST) From: Narvi To: Daniel Eischen In-Reply-To: Message-ID: <20030422004324.I29990-100000@haldjas.folklore.ee> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org cc: Julian Elischer Subject: Re: libkse -> libpthreads 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: Mon, 21 Apr 2003 21:55:15 -0000 On Mon, 21 Apr 2003, Daniel Eischen wrote: > On Mon, 21 Apr 2003, Julian Elischer wrote: > > > > > WE have a small problem.. when we started we had only on pthreads > > package and libKSE was teh heir.. > > No, libkse WAS libpthread. We renamed the library > temporarily until it was proven to work reasonably > well (I did the commit that renamed it). > > > now we have to live with libthr in the picture. > > it is possible that we should think of a naming scheme that > > allows all 3 libraries to have meaningful related names > > > > libc_r -> libpthreadM1 > > libthr -> libpthreadMM > > libkse -> libpthreadMN > > > > or something. > > The current naming scheme is fine. Libc_r is already > a well known name along with its shortcomings. Solaris > uses libthread for 1:1 as far as I can tell which would > seem to match libthr, and libpthread is the POSIX threads > library whose goal is to support POSIX as fully as > possible (scope process and scope system). > Solaris libthr is not a 1:1 thread library - the difference between libpthread and libthread is that libthread implements UI (sometimes also called Solaris) threads, and not pthreads. > I would object to libpthread{M1,MM,MN}. We already > had a name for libpthread. Libthr can live fine as > libthr or libthread. > No - if both provide the same API with potentially different implementation tradeoffs, then ythe libraries should be installed with different names and a symlink to the prefered one installed. At least for the moment it is not clear that one of teh libraries is a winner and will eliminate the other, so it would be evil to force people to explicitly link against one or the other causing future compatibility problems. Both provide the same pthreads API so there is no reasonable case for demanding that one of them can't have its SONAME be libpthpread.so.1 > -- > Dan Eischen >