Follow-up Comment #3, bug #44555 (project make):
To reply to a few points I didn't specifically address in my last comment:
* make isn't actually dropping into single-job mode, as can be seen from "make
--debug=j", but for some reason it's having trouble starting as many jobs as
requested.
* no, -O/--output-sync is not required to observe the problem
* I didn't spot anything that looked relevant in --trace
* like the Makefile generated by mkmk.sh, our build is nonrecursive.
Having no make step that takes appreciable CPU time is a lot like our case,
where frequently ccache hit rates exceed 95% (multiple developers share ccache
via nfs and work with substantially-similar source trees)
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?44555>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
