From owner-freebsd-current@FreeBSD.ORG Sat Nov 13 22:56:02 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 2FFA616A4CE; Sat, 13 Nov 2004 22:56:02 +0000 (GMT) Received: from celebrian.forsythia.net (galadriel.forsythia.net [64.81.65.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC74843D31; Sat, 13 Nov 2004 22:56:01 +0000 (GMT) (envelope-from amoran@forsythia.net) Received: from [10.200.1.101] (cerberus.forsythia.net [64.81.65.55]) iADMt6Jk049275; Sat, 13 Nov 2004 14:55:26 -0800 (PST) (envelope-from amoran@forsythia.net) In-Reply-To: <200411140051.42438.sla@smz.com.ua> References: <200411140051.42438.sla@smz.com.ua> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <103957F0-35C7-11D9-9133-000D93B1D960@forsythia.net> Content-Transfer-Encoding: 7bit From: Andrew Moran Date: Sat, 13 Nov 2004 14:55:07 -0800 To: Slava X-Mailer: Apple Mail (2.619) cc: freebsd-current@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: seemingly unfixable Spinlock error under 5.3? 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, 13 Nov 2004 22:56:02 -0000 I have tried mapping libc_r to libpthread using libmap.conf. it does not seem to have any effect.. Which doesn't surprise me too much since I can't find anything actually linked to libc_r anyway. :( --Andy On Nov 13, 2004, at 2:51 PM, Slava wrote: > more /usr/src/UPDATING > /20040303 > > man libmap.conf > >> I made the jump from 5.21 to 5.3 earlier and started getting the >> infamous "Fatal error 'Spinlock called when not threaded.' at line 83 >> in file /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 2)" >> everytime I ran gnucash. > >> I asked the freebsd-questions list but have gotten no response. So >> in desperation, I'm broadening my quest. I don't want to reinstall >> the server from scratch if there is another way to fix this error. >> Could there be something in my kernel configuration causing this? I >> can't find a reference to libc_r or libkse *anywhere*. :/ >> >> Does anyone have any ideas for me to try? Thank you for your time. >> >> --And >> >> _______________________________________________ >> freebsd-ports@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to >> "freebsd-ports-unsubscribe@freebsd.org" >> > > -- > Vyacheslav Bocharov > VB29-UANIC > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to > "freebsd-ports-unsubscribe@freebsd.org"