From owner-freebsd-threads@FreeBSD.ORG Wed Sep 26 00:53:13 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44E1316A41B; Wed, 26 Sep 2007 00:53:13 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id E78AE13C461; Wed, 26 Sep 2007 00:53:12 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.1/8.14.1/NETPLEX) with ESMTP id l8Q0r7lb019031; Tue, 25 Sep 2007 20:53:07 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.netplex.net [204.213.176.10]); Tue, 25 Sep 2007 20:53:07 -0400 (EDT) Date: Tue, 25 Sep 2007 20:53:07 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Alfred Perlstein In-Reply-To: <20070926004425.GF37370@elvis.mu.org> Message-ID: References: <20070926002038.GA56119@dragon.NUXI.org> <46F9A764.6000008@delphij.net> <20070926004425.GF37370@elvis.mu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: d@delphij.net, obrien@freebsd.org, freebsd-threads@freebsd.org Subject: Re: Renaming our threads libs X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 00:53:13 -0000 On Tue, 25 Sep 2007, Alfred Perlstein wrote: > > The current situation only makes sense to those that have been > watching the deal from day one, in "user land" confusion reigns > and we're punishing those that choose our platform but letting > it continue. And when someone has a threading bug, how are we suppose to know which thread library it is in? A simple 'ldd application' works if the thread libraries stay named differently. And a simple 'ls -l /lib/libpthread*' also works easily. I don't see how installing either libthr or libkse as libpthread is going to help. It's not clear which one is "libpthread" that way. The links make it clear, as well as 'ldd' output. And this can only help us when there are problem reports submitted. I really don't see how there is a big confusion. All ports should use -lpthread or -pthread, as well as other 3rd party applications. If someone is smart enough and wants to bypass the default threading library, then they are going to be less confused by always having the libraries consistently named regardless of what DEFAULT_THREAD_LIB is set to. -- DE