From owner-freebsd-current@FreeBSD.ORG Mon Sep 27 13:04:23 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 12D0616A4CE; Mon, 27 Sep 2004 13:04:23 +0000 (GMT) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1E1943D39; Mon, 27 Sep 2004 13:04:22 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) i8RD4LOA027754; Mon, 27 Sep 2004 09:04:21 -0400 (EDT) Date: Mon, 27 Sep 2004 09:04:21 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Andreas Klemm In-Reply-To: <20040927061627.GA1384@titan.klemm.apsfilter.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) cc: current@freebsd.org Subject: Re: Fatal error 'Spinlock called when not threaded.' ... (Re:FreeBSD 5.3-BETA6 available) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Sep 2004 13:04:23 -0000 On Mon, 27 Sep 2004, Andreas Klemm wrote: > On Sun, Sep 26, 2004 at 07:36:26PM -0400, Daniel Eischen wrote: > > On Sun, 26 Sep 2004, Andreas Klemm wrote: > > > > > Creating this helped (thanks to google ;-) > > > > > > /etc/libmap.conf: > > > libpthread.so.1 libc_r.so.5 > > > libpthread.so libc_r.so > > > > > > Has there been a change last recently ? > > > > No, not recently, but a few months ago. You're suppose to read > > src/UPDATING. Hint, search for entries 20040303 and 20040130. > > No I cannot be hitten by this. I upgrated multiple times via > several Beta stages. Read closer. This affects your ports, not the base system. Any older ports will be linked to libc_r, while newer ports will be linked to libpthread. Unless you rebuild all your ports from scratch, there will likely be ports linked to both libraries. Use 'ldd' on any executables that are giving you problems and you'll see. The problem is mostly due to shared libraries being linked to libc_r. Rebuilding a multithreaded application that depends on such a shared library will link the application to libpthread, but the shared library will still be linked to libc_r. This causes both libc_r and libpthread to be loaded when the program is run. ports@ will tell you to use 'portupgrade -af' to rebuild everything to remove dependencies to libc_r (make sure you get rid of /etc/libmap.conf first). -- Dan Eischen