Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 9 Jan 2015 18:10:24 +0000
From:      Antoine Brodin <antoine@FreeBSD.org>
To:        Sean Bruno <sbruno@freebsd.org>
Cc:        "sson \[via FreeBSD\]" <ml-node+s1045724n5979111h21@n5.nabble.com>, Marcus von Appen <mva@freebsd.org>, python@freebsd.org
Subject:   Re: python waf bypasses _MAKE_JOBS number
Message-ID:  <CAALwa8=q-3ZAQRxkgU0_EJL4qHYoA2%2BtE-=9%2BODSVi-uHeP2Aw@mail.gmail.com>
In-Reply-To: <54B0154B.80801@ignoranthack.me>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 9, 2015 at 5:52 PM, Sean Bruno <sbruno@ignoranthack.me> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAALwa8=q-3ZAQRxkgU0_EJL4qHYoA2%2BtE-=9%2BODSVi-uHeP2Aw>