From owner-freebsd-current@FreeBSD.ORG Sat Apr 10 06:09:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22E4B16A4CE for ; Sat, 10 Apr 2004 06:09:14 -0700 (PDT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 947BE43D1D for ; Sat, 10 Apr 2004 06:09:13 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.250.189) by smtp01.syd.iprimus.net.au (7.0.024) id 402BA9270145CE3B; Sat, 10 Apr 2004 23:09:12 +1000 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id 8ECF941DD; Sat, 10 Apr 2004 23:12:40 +1000 (EST) Date: Sat, 10 Apr 2004 23:12:40 +1000 From: Tim Robbins To: Matthias Schuendehuette Message-ID: <20040410131240.GA60597@cat.robbins.dropbear.id.au> References: <200404101154.45195.msch@snafu.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200404101154.45195.msch@snafu.de> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: libpthread? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Apr 2004 13:09:14 -0000 On Sat, Apr 10, 2004 at 11:54:45AM +0200, Matthias Schuendehuette wrote: > I don't think that's intended. Am I overlooking something here? Is > 'libkse/libpthread' still not ready for KDE/GNOME and that's subject to > improve in the future? Is there a (usable) way to use 'libc_r' for KDE > *only* other than mapping each single KDE app seperately? You need to rebuild all ports that link to thread libraries, or that link to libraries that link to thread libraries. I tried doing this with portupgrade -a, but had no luck. I ended up deleting all installed packages and starting from scratch. After doing this, KDE - and everything else I've tried - works perfectly with libpthread. I now have nothing at all linking to libc_r, and I went as far as removing /usr/lib/libc_r* to reassure myself of this. If you're still having problems after rebuilding all your ports from scratch, post to -current with more details, or submit a bug report. > Perhaps someone is willing to explain and conclude the "do"s and > "don't"s around the different threading libraries (not only) to me. The golden rule is: don't mix threading libraries within a program. If a program is linked to libc_r, so must all the other thread-aware libraries it links to be. The same goes for libpthread. The silver rule is: if you're using the nvidia driver, set up your libmap.conf so that everything gets linked to libc_r. Tim