Higher job count parallel builds (jam -j 4 for example) don't work
|Reported by:||meianoite||Owned by:||bonefish|
|Has a Patch:||no||Platform:||All|
When doing a "jam -j4" to build the image from scratch I receive a lot of missing targets, and end up having to repeat the build command 2+ times more to have it finally complete. And I'm not really sure the final image is sane, as there are errors regarding the copy of some files, and there's no sure-fire way of knowing it anyway, but I'll try comparing md5sums of the generated objects from one build and the other and see if I can filter out changes that are only related to hardcoding timestamps.
Building with "jam -j2" works, though, as plenty of devs are known to use this.
I guess the order of building and the dependencies between targets isn't fully fleshed out on our jamfiles.
I'm under the strong impression that this is known already, but I've searched Trac all over and haven't found a single ticket related to this; anyway, it's not anything critical, so I'm filing this one as "enhancement". Still, doing such parallel build under Haiku itself is fantastic to test the IO subsystem, the scheduler, and to demo how Haiku will be able to decode 8+ streams of video, build itself, and not drop a single frame in the process ;)
Build logs attached; same build, each an additional run of "jam -q -j4" (5 runs in total)