From owner-freebsd-questions@FreeBSD.ORG Fri Oct 27 00:43:18 2006 Return-Path: X-Original-To: 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 81AF516A403 for ; Fri, 27 Oct 2006 00:43:18 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DBE943D55 for ; Fri, 27 Oct 2006 00:43:18 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 1C1AA1A4D82; Thu, 26 Oct 2006 17:43:18 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 494A951374; Thu, 26 Oct 2006 20:43:14 -0400 (EDT) Date: Thu, 26 Oct 2006 20:43:14 -0400 From: Kris Kennaway To: "Tuc at T-B-O-H.NET" Message-ID: <20061027004314.GA69594@xor.obsecurity.org> References: <20061026231733.GA68808@xor.obsecurity.org> <200610270034.k9R0YqLt037766@himinbjorg.tucs-beachin-obx-house.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zYM0uCDKw75PZbzx" Content-Disposition: inline In-Reply-To: <200610270034.k9R0YqLt037766@himinbjorg.tucs-beachin-obx-house.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-questions@freebsd.org, Kris Kennaway Subject: Re: Fatal error 'Spinlock called when not threaded.' X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2006 00:43:18 -0000 --zYM0uCDKw75PZbzx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Oct 26, 2006 at 08:34:52PM -0400, Tuc at T-B-O-H.NET wrote: > > On Thu, Oct 26, 2006 at 06:33:09PM -0400, Tuc at T-B-O-H.NET wrote: > > > Hi, > > >=3D20 > > > Thanks... Any idea where to look for the answer? I did find > > > references, but to "UPDATING" that didn't exist. Wondered how all=3D20 > > > of a sudden items I haven't recompiled in a while started having > > > it. > >=20 > > You had old packages linked against an old version of the library from > > a previous revision of FreeBSD, and they only broke when your recent > > update changed one of them to link to both versions. > > > FreeBSD himinbjorg.tucs-beachin-obx-house.com 5.5-RELEASE-p2 FreeBSD 5.5-= RELEASE-p2 #0: Tue Jun 20 15:27:48 EDT 2006 root@himinbjorg.tucs-beachi= n-obx-house.com:/usr/src/sys/i386/compile/HIMINBJORG53noagp i386 >=20 > As you see, I haven't updated my base OS in 4 months. OK, but that doesn't rule out what I said. You have *some* files still left over from an older version of FreeBSD, in particular, including the following: a) an old copy of a thread library b) old packages linked to this old thread library=20 > > > > portupgrade -fa is the most convenient way to solve this. > >=20 > That scares me to no ever loving end. I usually end up > with issues. I'm doing a "portupgrade -rf pkg-config\*" for the > 3rd time right now. It hasn't worked properly the other 2 > times. Probably for the same reason, i.e. you're not updating a consistent subset of your packages. There are packages that do not depend on pkg-config that probably need to be updated too, and since you're not updating them then you'll break things that require the new version. In fact, doing a portupgrade -fa is the usual way you *fix* such inconsistencies, as I've already said. Kris --zYM0uCDKw75PZbzx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFQVYhWry0BWjoQKURAtEFAKDCWSi5oT0EnOKNQ9PRwK9m5vRxqwCg/WaV xbdD/WsdWAMRTgwqe5mbScM= =5OZt -----END PGP SIGNATURE----- --zYM0uCDKw75PZbzx--