From owner-freebsd-questions@FreeBSD.ORG  Sun Feb  8 08:33:17 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 98B3816A4CE
	for <freebsd-questions@freebsd.org>;
	Sun,  8 Feb 2004 08:33:17 -0800 (PST)
Received: from elkins.org (user41.net272.fl.sprint-hsd.net [64.45.235.41])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7473843D1D
	for <freebsd-questions@freebsd.org>;
	Sun,  8 Feb 2004 08:33:17 -0800 (PST)	(envelope-from bsd@elkins.org)
Received: from kathix.elkins ([192.168.0.10])
	by elkins.org with esmtp (Exim 3.36 #1 (Debian))
	id 1Aprrw-0005m2-00
	for <freebsd-questions@freebsd.org>; Sun, 08 Feb 2004 11:33:16 -0500
From: Jeff Elkins <bsd@elkins.org>
To: freebsd-questions@freebsd.org
Date: Sun, 8 Feb 2004 11:33:15 -0500
User-Agent: KMail/1.5.4
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402081133.15941.bsd@elkins.org>
Subject: 5.2 portupgrade: kde-3.2.0
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Feb 2004 16:33:17 -0000

Fatal error 'Spinlock called when not threaded.' at line 83 in 
file /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 0)
Abort trap (core dumped)

I'm unable to upgrade kde t o 3.2 due to the error above in kdelibs-3.2.0. 
Googling the error wasn't very helpful...the most enlightning message said 
'something in your system is hosed,' or words to that effect.

What do I need to do to correct this problem?

Thanks,

Jeff Elkins