Jonathan Perkin <jperkin%pkgsrc.org@localhost> writes:
Why does it need MAKE_JOBS_SAFE=no? Notably this will cause bob
builds that use the dynamic scheduler to be done at -j1. I realise
this is a "I don't care" for most people, but it still seems wrong to
be setting that variable yet still expecting to use parallel jobs, and
I don't think it's necessary or even correct.
I'm not really sure what you mean "done at -j1". Do you mean bob's
scheduler will expect concurrency of 1, but it will actually be
MAKE_JOBS, and thus be higher than expectations, which is wrong? If so,
I see your point.
- don't set MAKE_JOBS_SAFE=no, after verifying by code reading that
there won't actually be any use of -jN. Or if there is, set
GOMAXPROCS=1 for that package (always, because the -j mechanism has
the token). Consider that passing GOMAXPROCS=1 to 'go build' is how
you spell -jN on the command line, and call it right.
and having written that I think the 2nd option is the right answer for
now.