From owner-freebsd-python@FreeBSD.ORG Sun Feb 2 10:00:01 2014 Return-Path: Delivered-To: freebsd-python@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8DB7ACF for ; Sun, 2 Feb 2014 10:00:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 79C241EAD for ; Sun, 2 Feb 2014 10:00:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s12A015t056472 for ; Sun, 2 Feb 2014 10:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s12A01f6056471; Sun, 2 Feb 2014 10:00:01 GMT (envelope-from gnats) Date: Sun, 2 Feb 2014 10:00:01 GMT Message-Id: <201402021000.s12A01f6056471@freefall.freebsd.org> To: freebsd-python@FreeBSD.org Cc: From: Olaf Zaplinski Subject: Re: ports/186192: lang/python27: building python27-2.7.6_1 fails X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Olaf Zaplinski List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Feb 2014 10:00:01 -0000 The following reply was made to PR ports/186192; it has been noted by GNATS. From: Olaf Zaplinski To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/186192: lang/python27: building python27-2.7.6_1 fails Date: Sun, 02 Feb 2014 10:53:14 +0100 Am 01.02.2014 19:49, schrieb Garrett Cooper: > This PR is similar ports/147291. > The problem is that src.conf isn’t sourced in the ports build infrastructure, so any variables plugged into src.conf won’t get picked up when building ports. > Adding WITHOUT_NIS=yes to /etc/make.conf will work around the issue though. > I’m not sure if looking for *_failed.so would be a good idea when creating the plist, but it would at least avoid the install/package creation issue. > Thanks! > -Garrett > Thanks! I had no idea that this make.conf options still do exist in 10.0 because: [root@betsy ~/log]# man make.conf|grep NIS [root@betsy ~/log]# Cheers Olaf