On 06/01/2024 17:52, Peter Humphrey wrote:
In other cases, there may be a hundred separate tasks, make fires off a hundred tasks shared amongst all the resource it can find, and sits back and waits.
And that's how the very first installation goes, with single-host distcc. Then, when it gets to gcc, it collapses to 2 threads and everything gained so far is lost many-fold. (I set USE=-fortran to avoid pointless recompilation, since nothing needs it here.)
So if it's consistently gcc that collapses to two threads, then something (maybe explicit settings, maybe dependencies, maybe yadda yadda) is telling make that only two jobs can run at the same time else they'll trip over each other.
Could be a dev has hard-coded the "two jobs" rule to make those random crashes go away :-) Or maybe they found the problem, and that's why only two jobs can run in parallel.
Cheers, Wol
