From owner-freebsd-python@FreeBSD.ORG Tue Jan 6 23:50:59 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 D5965FA8 for ; Tue, 6 Jan 2015 23:50:59 +0000 (UTC) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 B5A93644EA for ; Tue, 6 Jan 2015 23:50:59 +0000 (UTC) Received: from [10.12.76.127] (llnw-corp-src.phx2.llnw.com [69.164.56.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id B556C192A3B for ; Tue, 6 Jan 2015 23:50:58 +0000 (UTC) Message-ID: <54AC74E0.4050404@ignoranthack.me> Date: Tue, 06 Jan 2015 15:50:56 -0800 From: Sean Bruno Reply-To: sbruno@freebsd.org User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: freebsd-python@freebsd.org Subject: python waf bypasses _MAKE_JOBS number Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit 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: Tue, 06 Jan 2015 23:50:59 -0000 -----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? sean -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJUrHTgXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5ktAsH/3P9StdKr01WkEYjoQ8oG8S/ J6ZXmOsCAeG98rehng9+UuRFvD3ifFdFIxHdFRtVIFDe8JGBU9AGkusGHLzyFUnT M4CVR3mQh6qlxdE/d3Hp7gNOlnssA/BXwPnKSLmK2FZVacgeCtUA/d01B7KDTADz 6mhpGg5eMgKOXfnAExMI4MIfVVTlfzdcj62DuaQjTTx0PpcmTxNVs+5QnTOcRyBc qZFoorZr5x97L4PGlausDe8CVGTzOGs31bHgxCJZF28tQ0L49Qyq6tEo6DrK+ngB /7u0hL9ITxMN94m57uzZDp8T6Wkr8q5eHys7J7GMMRjm8QrtNEFvDl/X3M/Dweg= =nAQ4 -----END PGP SIGNATURE-----