Alexey,
You wrote:
Therefore, the patch I suggested uses another approach. If the next
dependency has the "wait" flag set, make does not consider it and the
dependencies further in the list until the jobs already running
complete.
and then
For example, the following Makefile:
<<<<
a: x1 .WAIT x2
b: x2 .WAIT x3
<<<<
when run with "make -j a b", starts the targets in the following
order: x1 and x3 simultaneously, then, as both them are finished, x2.
Indeed, the ordering information cannot be stored only in the
dependency chain.
So, if "x2" is in the "wait" state, why is make considering "x3" ?
Christophe.
_______________________________________________
Help-make mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-make
