[bug #22923] option to prevent interspersed output in parallel builds

2010-01-14 Thread Ilguiz Latypov
Follow-up Comment #5, bug #22923 (project make): Another idea mentioned in a Python bug discussion on file handles contention is to have each spawned make process redirect stdout and stderr of its spawned actions to a socket opened by the main make process. (Perhaps, each make process could do

[bug #22923] option to prevent interspersed output in parallel builds

2010-01-14 Thread Paul D. Smith
Follow-up Comment #6, bug #22923 (project make): I don't really see the difference between comment #5 and the original description. I've addressed why this is hard to do in comment #2. ___ Reply to this item at:

[bug #22923] option to prevent interspersed output in parallel builds

2010-01-14 Thread Howard Chu
Follow-up Comment #7, bug #22923 (project make): Reaching back 25 years again, this is basically what Alliant Concentrix parallel make did. It prefixed each output line with the job number |1|, |2| and so on. (This is also why in my original proposal for make -j, I used different numbered job

[bug #28134] inconsistent reporting of linux kernel builds with -j2

2010-01-14 Thread Howard Chu
Follow-up Comment #3, bug #28134 (project make): As a complete digression, and based on 26 years of doing parallel builds (damn it's been a long time), I just wanted to point out that you can generally use 50% more jobs than your number of CPUs/cores. E.g., for a dual-core machine, use make -j3.