From owner-freebsd-current@FreeBSD.ORG Tue Feb 10 20:21:15 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 6B21316A4CF for ; Tue, 10 Feb 2004 20:21:15 -0800 (PST) Received: from ms-smtp-02-eri0.southeast.rr.com (ms-smtp-02-lbl.southeast.rr.com [24.25.9.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AEA943D45 for ; Tue, 10 Feb 2004 20:21:15 -0800 (PST) (envelope-from jason@ec.rr.com) Received: from ec.rr.com (cpe-024-211-231-149.ec.rr.com [24.211.231.149]) i1B4LCq3026430; Tue, 10 Feb 2004 23:21:12 -0500 (EST) Message-ID: <4029ADA0.8000508@ec.rr.com> Date: Tue, 10 Feb 2004 23:20:48 -0500 From: Jason User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20040210 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <402A5EDE.7050501@ec.rr.com> <20040211035444.GA46239@xor.obsecurity.org> In-Reply-To: <20040211035444.GA46239@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine cc: current@freebsd.org Subject: Re: bittorrent has problems after an update to currnet 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: Wed, 11 Feb 2004 04:21:15 -0000 Kris Kennaway wrote: >On Wed, Feb 11, 2004 at 11:57:02AM -0500, Jason wrote: > > >>$ btdownloadgui.py >>Fatal error 'Spinlock called when not threaded.' at line 83 in file >>/usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 2) >>Abort trap (core dumped) >>$ >> >>I updated my whole system to current on monday and had problems with >>bittorrent after I did a portupgrade. There was a missing libwx_gtk.so >>that I fixed, then it was this error I can not figure out. Anyone have >>any ideas? My only idea is the code doesn't like the new libs. >> >> > >Something is linked against two thread libraries - this has been >discussed extensively here and on ports@. > >Kris > > Ok, after checking the archives I found that everything python is broken, not because of linking to 2 thread libraries but because of a bug. I tried to confirm this on my machince and found out this for python: $ ldd /usr/local/bin/python /usr/local/bin/python: libpthread.so.1 => /usr/lib/libpthread.so.1 (0x28129000) libutil.so.4 => /lib/libutil.so.4 (0x2814e000) libstdc++.so.4 => /usr/lib/libstdc++.so.4 (0x2815a000) libm.so.2 => /lib/libm.so.2 (0x2821d000) libc.so.5 => /lib/libc.so.5 (0x28238000) So unless there is a better fix or I am wrong(please correct me if I am) I will cvsup and have to rebuild everything, or the world and python.