From owner-freebsd-python@FreeBSD.ORG Wed Jan 7 07:24:37 2015 Return-Path: Delivered-To: freebsd-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 EF35A6EE; Wed, 7 Jan 2015 07:24:37 +0000 (UTC) Received: from smtprelay06.ispgateway.de (smtprelay06.ispgateway.de [80.67.31.95]) (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 AF86E1BA3; Wed, 7 Jan 2015 07:24:37 +0000 (UTC) Received: from [89.182.174.158] (helo=localhost) by smtprelay06.ispgateway.de with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84) (envelope-from ) id 1Y8kvr-0005Se-3l; Wed, 07 Jan 2015 08:21:31 +0100 Date: Wed, 7 Jan 2015 08:21:32 +0100 From: Marcus von Appen To: sbruno@freebsd.org Subject: Re: python waf bypasses _MAKE_JOBS number Message-ID: <20150107072132.GA1050@medusa.sysfault.org> Reply-To: Marcus von Appen Mail-Followup-To: sbruno@freebsd.org, freebsd-python@freebsd.org References: <54AC74E0.4050404@ignoranthack.me> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline In-Reply-To: <54AC74E0.4050404@ignoranthack.me> User-Agent: Mutt/1.5.23 (2014-03-12) X-Df-Sender: MTEyNTc0Mg== Cc: freebsd-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: Wed, 07 Jan 2015 07:24:38 -0000 --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On, Wed Jan 07, 2015, Sean Bruno wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Hey, so ... because qemu has a bug in it, we're trying to enforce no > SMP behaviour in builds. > > Turns out that python waf bypasses all of ports logic and probes for > the number of cpus and does its own thing. We noted this in our > builds as they locked up when using qemu due to a bug. > > Can this behaviour be investigated (configure behaviour) by some > python knowledgeable folks? Can you point us to the waf build logic for the qemu port? Looking at emulators/qemu, I do not see anything of relevance. Cheers Marcus --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSs3nwACgkQi68/ErJnpkf6SQCg0Txy+RMEPRvbds0ZnOTUskp0 fkUAoLv2VE0VTRVKtobNeCX+DWUkndwa =goLV -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu--