From owner-freebsd-threads@FreeBSD.ORG Wed Sep 26 13:15:14 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 3B34216A41B; Wed, 26 Sep 2007 13:15:14 +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 13DF413C4A5; Wed, 26 Sep 2007 13:15:13 +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 l8QDF5Js012555; Wed, 26 Sep 2007 09:15:05 -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]); Wed, 26 Sep 2007 09:15:05 -0400 (EDT) Date: Wed, 26 Sep 2007 09:15:05 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: "David O'Brien" In-Reply-To: <20070926045726.GC60798@dragon.NUXI.org> Message-ID: References: <20070926002038.GA56119@dragon.NUXI.org> <46F9A764.6000008@delphij.net> <20070926004425.GF37370@elvis.mu.org> <20070926045726.GC60798@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: d@delphij.net, 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 13:15:14 -0000 On Tue, 25 Sep 2007, David O'Brien wrote: > On Tue, Sep 25, 2007 at 08:53:07PM -0400, Daniel Eischen wrote: >> 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? > > Because if they linked with -lpthreads they were using libthr (after its > repo-copied). If they say they linked with -lkse - we know that that is. Asking them how they linked is after the fact and history tells us that we won't get a accurate answer to this question. > There is also 'ldd' output. Only in folks that have been in the thick of > our thread libs since the day 7.0 was born have the notion that > libpthread is anything other than what is today called "libthr". > > >> 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. > > Its perfectly clear [after a repo-copy rename]. It's not perfectly clear when DEFAULT_THREAD_LIB is anything other than libthr. I want -pthread to do the right thing regardless of which library is DEFAULT_THREAD_LIB, because -pthread is what we're telling everyone to use (well, it's what GCC is telling everyone to use). -- DE