Re: python nproc vs MAKE_JOBS issues

[Thomas Klausner <wiz%gatalith.at@localhost>]

On Mon, Nov 11, 2024 at 12:28:24PM +0000, Jonathan Perkin wrote:
> * On 2024-11-11 at 12:10 GMT, Thomas Klausner wrote:
> 
> > On Mon, Nov 11, 2024 at 11:57:11AM +0000, Jonathan Perkin wrote:
> > > I've seen a few similar things to this recently where python modules are
> > > being built with complete disregard to MAKE_JOBS, and instead are just
> > > spawning a thread for each CPU they find.  For example:
> > 
> > This seems to be py-maturin's default, to use one job per CPU.
> > 
> > > Do any python folks know what is causing this and are able to fix it?
> > 
> > Try the attached patch.
> 
> That doesn't work unfortunately.  The "maturin build" command has this flag:
> 
>   -j, --jobs <N>                Number of parallel jobs, defaults to # of CPUs
> 
> but I don't know how to pass that through the python stuff.

We're using 'build' to build and that has a '-C' flag to pass
arguments through to the actual build backend. We use WHEEL_ARGS to
extend the arguments passed to it in lang/python/wheel.mk.

If my patch doesn't work, please try to find a version that does.
 Thomas