From owner-freebsd-threads@FreeBSD.ORG Wed Sep 26 04:57:33 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 4E97416A41A; Wed, 26 Sep 2007 04:57:33 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 1197513C45B; Wed, 26 Sep 2007 04:57:32 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id l8Q4vQYm060938; Tue, 25 Sep 2007 21:57:26 -0700 (PDT) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.1/8.14.1/Submit) id l8Q4vQx7060937; Tue, 25 Sep 2007 21:57:26 -0700 (PDT) (envelope-from obrien) Date: Tue, 25 Sep 2007 21:57:26 -0700 From: "David O'Brien" To: Daniel Eischen Message-ID: <20070926045726.GC60798@dragon.NUXI.org> 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 Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.16 (2007-06-09) 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: obrien@freebsd.org List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 04:57:33 -0000 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. 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]. > The links make it clear, Only if we have access to the user's build machine - which we won't. If one wants to easily switch between thread libs for an already-compiled binary - we have /etc/libmap.conf for that. -- -- David (obrien@FreeBSD.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? Let's not play "Jeopardy-style quoting"