From owner-freebsd-python@FreeBSD.ORG Fri Jan 9 23:29:18 2015 Return-Path: Delivered-To: python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7E96731D; Fri, 9 Jan 2015 23:29:18 +0000 (UTC) Received: from smtprelay02.ispgateway.de (smtprelay02.ispgateway.de [80.67.18.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 376D6E04; Fri, 9 Jan 2015 23:29:17 +0000 (UTC) Received: from [80.67.16.130] (helo=webmailfront01.ispgateway.de) by smtprelay02.ispgateway.de with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.84) (envelope-from ) id 1Y9izM-0007Oo-Ll; Sat, 10 Jan 2015 00:29:08 +0100 Received: from a89-182-73-111.net-htp.de (a89-182-73-111.net-htp.de [89.182.73.111]) by webmail.df.eu (Horde Framework) with HTTP; Sat, 10 Jan 2015 00:29:08 +0100 Date: Sat, 10 Jan 2015 00:29:08 +0100 Message-ID: <20150110002908.Horde.QrB60C0_PExk9ypkaJhFiA1@webmail.df.eu> From: Marcus von Appen To: sbruno@freebsd.org, Sean Bruno , sson@freebsd.org Subject: Re: python waf bypasses _MAKE_JOBS number References: <54AC74E0.4050404@ignoranthack.me> <20150107072132.GA1050@medusa.sysfault.org> <54AD5BB9.2060701@ignoranthack.me> <1420653060968-5979111.post@n5.nabble.com> <20150109183334.Horde.DDLUOEFT2TrMFUcP63h_9Q1@webmail.df.eu> <54B0154B.80801@ignoranthack.me> <54B019C1.7090704@ignoranthack.me> In-Reply-To: <54B019C1.7090704@ignoranthack.me> Reply-to: mva@freebsd.org User-Agent: Internet Messaging Program (IMP) H5 (6.0.4) Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline X-Df-Sender: ZnJlZWJzZEBzeXNmYXVsdC5vcmc= Cc: Antoine Brodin , python@freebsd.org X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jan 2015 23:29:18 -0000 Sean Bruno : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 01/09/15 11:10, Antoine Brodin wrote: >> On Fri, Jan 9, 2015 at 5:52 PM, Sean Bruno >> wrote: >>> Marcus: >>> >>> The thing that I would like "fixed" is python waf ignoring the >>> fact that it should not try and detect the number of CPUs on the >>> system. >>> >> >> Let me rephrase the problem, there are some problems in some >> individual ports using waf. Those ports do not respect >> ${MAKE_JOBS_NUMBER}, especially when MAKE_JOBS_NUMBER=1. This >> breaks qemu which is not multi job friendly (people using qemu >> have DISABLE_MAKE_JOBS=yes which sets MAKE_JOBS_NUMBER to 1). >> >> Cheers, >> >> Antoine >> > > YES. :-) Sorry for the confusion. Just to be a bit more specific: we are not talking about a waf port, but about some (still unknown) waf scripts in the upstream package, correct? Since this is the usual way, waf is used. Please point us to the correct scripts/call hierarchy/whatever that allows us to investigate, what the port actually does at the build phase. waf issues usually need to be fixed (since it's somewhat similar to a cmake, scons or autotools configuration/build file) on the problematic port or via injection, hence we need the information about how the build is done or at least a pointer, where to look at. I'm leaving the threading issue aside here, since (for now) there is not enough information (for me) to address this. Let's get the build issue sorted out first, then take a look at Python's threading support for non-amd64 and non-i386 platforms on FreeBSD. Cheers Marcus