From owner-freebsd-stable@FreeBSD.ORG Mon Jan 17 15:34:10 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE79F16A4CE; Mon, 17 Jan 2005 15:34:10 +0000 (GMT) Received: from voodoo.oberon.net (voodoo.oberon.net [212.118.165.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96D6F43D1D; Mon, 17 Jan 2005 15:34:10 +0000 (GMT) (envelope-from krion@voodoo.oberon.net) Received: from krion by voodoo.oberon.net with local (Exim 4.43 (FreeBSD)) id 1CqYsv-000Piy-1m; Mon, 17 Jan 2005 16:33:41 +0100 Date: Mon, 17 Jan 2005 16:33:41 +0100 From: Kirill Ponomarew To: "Hamilton, Kent" Message-ID: <20050117153341.GO93155@voodoo.oberon.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-NCC-Regid: de.oberon X-NIC-HDL: KP869-RIPE cc: freebsd-stable@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: Qt33 Build Problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 15:34:11 -0000 On Mon, Jan 17, 2005 at 08:59:58AM -0600, Hamilton, Kent wrote: > I have two systems that I'm having problems building qt33 on. Both are > RELENG_5_3 with perl-threaded-5.8.5 on dual processor Dell PowerEdge > systems. > > I'm getting the same error building on both systems. I'm trying to build > with all the config options turned on (CUPS, NAS, OpenGL, XFt). The uic > that gets built dies with a thread error so I can't finish the build. > > The error is: > Fatal error 'Spinlock called when not threaded.' at line 83 in file > /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 0) > Abort (code dumped) > kernel: pid 14119 (uic), uid 0: existed on signal 6 (core dumped) > > I'd really appreciate any suggestions. > > I don't subscribe to freebsd-ports so if you are answering on that list > please add me to the message. You can rebuild all your ports, or use libmap.conf(5), or even better, search the archives to understand this problem. We should really put it into FAQ, if it's not there. -Kirill