Follow-up Comment #1, bug #44555 (project make):
How do you know that it falls back to one job at a time? Does make actually
print out the message it usually does when it gives up on parallelism?
Or, do you just observe the build taking a long time and watch the commands
being invoked, and see that they are running one at a time? Or, are you going
by output only?
Is your build environment using a recursive make model, or does it use only
one invocation of make?
If you run make with the --trace flag, does it show anything different between
the "good" and "bad" runs?
I assume you are not enabling the new output sync mode when you invoke make?
I find it very bizarre that the change from fork() to vfork() would cause this
behavior... the commit you mention literally does nothing but switch from
vfork() to fork() (and the associated config changes). In general it should
never be the case that this change causes problems (it can cause problems to
go from fork() to vfork(), of course, depending on what you do after you
fork).
_______________________________________________________
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
