From owner-freebsd-python@FreeBSD.ORG Thu Mar 22 12:50:11 2012 Return-Path: Delivered-To: freebsd-python@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7883106566B for ; Thu, 22 Mar 2012 12:50:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 713C68FC08 for ; Thu, 22 Mar 2012 12:50:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q2MCoB5R051876 for ; Thu, 22 Mar 2012 12:50:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2MCoBek051875; Thu, 22 Mar 2012 12:50:11 GMT (envelope-from gnats) Date: Thu, 22 Mar 2012 12:50:11 GMT Message-Id: <201203221250.q2MCoBek051875@freefall.freebsd.org> To: freebsd-python@FreeBSD.org From: Jan Mikkelsen Cc: Subject: Re: ports/163467: Ports using python 2.7 and " waf" intermittently hang on build/installation X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jan Mikkelsen List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2012 12:50:11 -0000 The following reply was made to PR ports/163467; it has been noted by GNATS. From: Jan Mikkelsen To: Mel Flynn Cc: bug-followup@FreeBSD.org Subject: Re: ports/163467: Ports using python 2.7 and "waf" intermittently hang on build/installation Date: Thu, 22 Mar 2012 23:36:28 +1100 Hi Mel, Sorry about taking so long to get back to you. I have python installed without WITH_SEM already. The build process is = logged and I have the complete system checked into our local Perforce = server. These are the arguments to exec on the last build: Executing, with stdin from /dev/null: arg[0] =3D '/usr/sbin/chroot' arg[1] =3D '/home/janm/p4/freebsd-image-std-2011.1/work/build-chroot' arg[2] =3D '/usr/bin/env' arg[3] =3D '-' arg[4] =3D = 'PATH=3D/sbin:/bin:/usr/bin:/usr/sbin:/usr/local/sbin:/usr/local/bin:/usr/= X11R6/bin' arg[5] =3D '/bin/sh' arg[6] =3D '-cxe' arg[7] =3D ' cd /usr/ports/lang/python27 env NO_MTREE=3D"true" make package = WRKDIRPREFIX=3D/ports-work = PKGFILE=3D'/ports-packages/python27-2.7.2_3.tbz' BATCH=3Dyes = NODEPENDS=3Dyes PACKAGE_BUILDING=3Dyes=20 ' I also had the output to stdout and stderr from that build and noticed = that the configure output was still showing that Posix semaphores were = in use. Looking at the makefile, I see this: post-patch: .if defined(WITH_SEM) .if ${OSVERSION} >=3D 701106 @cd ${WRKSRC} && ${PATCH} ${PATCH_ARGS} < = ${PATCHDIR}/extra-patch-setup.py .endif .endif That patch only disables HAVE_SEM_OPEN and HAVE_SEM_TIMEDWAIT when = WITH_SEM is not set on FreeBSD 6 and earlier. In the build log I see = (without WITH_SEM set): checking for sem_open... yes checking for sem_timedwait... yes The interesting test would be to explicitly disable HAVE_SEM_OPEN and = HAVE_SEM_TIMEDWAIT in the python build. I'll set up a test and see if we = have any builds hang. Have you discovered anything new since your email? Thanks, Jan Mikkelsen On 19/03/2012, at 10:54 PM, Mel Flynn wrote: > Hi Jan, >=20 > if you have python built with semaphores could you reinstall without > them and see if you can still reproduce the problem? > If you haven't, please do show: > make -C /usr/ports/lang/python27 show-config >=20 > --=20 > Mel