From owner-freebsd-current@FreeBSD.ORG  Fri Feb  6 06:06:17 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 3C4E416A4CE
	for <current@FreeBSD.org>; Fri,  6 Feb 2004 06:06:17 -0800 (PST)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B21AF43D46
	for <current@FreeBSD.org>; Fri,  6 Feb 2004 06:06:15 -0800 (PST)
	(envelope-from eischen@vigrid.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i16E6Efo004123;
	Fri, 6 Feb 2004 09:06:14 -0500 (EST)
Date: Fri, 6 Feb 2004 09:06:14 -0500 (EST)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Kris Kennaway <kris@obsecurity.org>
In-Reply-To: <20040206042328.GA45061@xor.obsecurity.org>
Message-ID: <Pine.GSO.4.10.10402060855020.1294-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@FreeBSD.org
Subject: Re: python ports broken (sem_destroy: Resource temporarily
	unavailable)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2004 14:06:17 -0000

On Thu, 5 Feb 2004, Kris Kennaway wrote:

> On Thu, Feb 05, 2004 at 06:37:41PM -0500, Daniel Eischen wrote:
> 
> > > > Actually lots of the package builds seem to be hanging in this way.
> > > 
> > > I'm looking at this but don't see anything wrong yet.  I've
> > > just started a buildworld and will see if I can get sem_destroy()
> > > to fail.
> > > 
> > > FYI, sem_destroy() returns -1 with errno = EBUSY when there
> > > are waiters waiting on the semaphore.
> > 
> > I think I fixed the problem (see last commit to libc/gen/sem.c).
> > Please continue to let me know of any problems you find.
> 
> Nope, still broken.  Can you confirm that you can build e.g. the
> py23-bsddb3-4.1.6_1 port?  It hangs for me here:
> 
> [...]
> byte-compiling /usr/local/lib/python2.3/site-packages/bsddb3/tests/test_queue.py to test_queue.pyc
> byte-compiling /usr/local/lib/python2.3/site-packages/bsddb3/tests/test_recno.py to test_recno.pyc
> byte-compiling /usr/local/lib/python2.3/site-packages/bsddb3/tests/test_thread.py to test_thread.pyc

Thanks, that was a good test.  I'm behind a slow dial-up so I
appreciate the smallish distfile.

I committed a fix to libc/gen/sem.c.  The port appears to build
(and install) OK for me now.

-- 
Dan Eischen