#11012: jam -j fails ----------------------------+---------------------------- Reporter: Anarchos | Owner: bonefish Type: bug | Status: reopened Priority: normal | Milestone: Unscheduled Component: Build System | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 0 | Platform: x86 ----------------------------+---------------------------- Comment (by bonefish): Manually removing something in a subdirectory of generated/build_package is not simulating a parallel build. For a build feature a single target is used for the extraction of all packages associated with that build feature. All targets (like the headers directory) that are associated with attributes of the build feature depend on that main target. So all users of the build feature can depend on any of the targets and the extraction of all packages is guaranteed. Unless you manually manipulate the extraction directory so that it looks like the main target doesn't have to be made. Or you somehow manage to interrupt jam between extracting the two packages (a regular build failure shouldn't cause it). That being said, I wonder if your jam fix is correct. I'm not particularly familiar with the jam sources, but the patch(es) suggested on the jamming mailing list were rather different. The first one I saw (cf. [http://maillist.perforce.com/pipermail/jamming/2010-June/002421.html this mail] was proposed by Chuck Homic in June 2010. The thread continues (with a break) through December 2010 (it isn't that long) with a few more analysis and patch suggestions. Also note that boost jam is a fork of a rather old version of the mainline jam. -- Ticket URL: <https://dev.haiku-os.org/ticket/11012#comment:6> Haiku <https://dev.haiku-os.org> Haiku - the operating system.