From owner-freebsd-current@FreeBSD.ORG Sat Apr 10 14:35:21 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 96A7D16A4CE; Sat, 10 Apr 2004 14:35:21 -0700 (PDT) Received: from clever.eusc.inter.net (clever.eusc.inter.net [213.73.101.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5430E43D1D; Sat, 10 Apr 2004 14:35:21 -0700 (PDT) (envelope-from msch@snafu.de) Received: from dial-76-176.de.inter.net ([213.73.76.176] helo=current.best-eng.de) by clever.eusc.inter.net with esmtp (Exim 3.36 #4) id 1BCQ8G-0004Ru-00; Sat, 10 Apr 2004 23:35:20 +0200 Received: from current.best-eng.de (localhost.best-eng.de [127.0.0.1]) by current.best-eng.de (8.12.11/8.12.11) with ESMTP id i3ALZJrb064968; Sat, 10 Apr 2004 23:35:19 +0200 (CEST) (envelope-from matthias@current.best-eng.de) Received: from localhost (localhost [[UNIX: localhost]]) by current.best-eng.de (8.12.11/8.12.11/Submit) id i3ALZI2t064967; Sat, 10 Apr 2004 23:35:18 +0200 (CEST) (envelope-from matthias) From: Matthias Schuendehuette Organization: Micro$oft-free Zone To: Daniel Eischen Date: Sat, 10 Apr 2004 23:35:17 +0200 User-Agent: KMail/1.6.1 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200404102335.18433.msch@snafu.de> X-Mailman-Approved-At: Sun, 11 Apr 2004 05:44:56 -0700 cc: freebsd-current@freebsd.org cc: Tim Robbins Subject: Re: libpthread? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: msch@snafu.de 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 21:35:21 -0000 X-List-Received-Date: Sat, 10 Apr 2004 21:35:21 -0000 Hi Dan, Hi you others, On Saturday 10 April 2004 17:10, Daniel Eischen wrote: > On Sat, 10 Apr 2004, Tim Robbins wrote: > > You don't need to rebuild any ports if you globally > map libc_r to libpthread with /etc/libmap.conf. Over > time, when all your ports are upgraded at your leisure, > references to libc_r will be removed. Of course, > portupgrade -af would do the trick much quicker... Yeah, that was the key-paragraph! I read this already in UPGRADING but obviously didn't understand it fully... 'portupgrade -af' is not an option here because of my ISDN-Line (64 kbit/s). I'm perhaps one of the last users of hm's 'i4b'-package... :-) > > 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. > > If you are coming from 5.2.1-RELEASE and before, and trying > to upgrade to -release, the default threading library changed > from libc_r to libpthread. This would explain how you would > be mixing threading libraries and why you need to (at least > temporarily) use /etc/libmap.conf to choose one. Yes, I'm coming from 5.0-current... :-) > > The silver rule is: if you're using the nvidia driver, set up > > your libmap.conf so that everything gets linked to libc_r. So that's the "show-stopper" for the nvidia-driver - at least for me for the near future until it works with 'libpthread'. Thank you very much for your explanations! -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F