#28224 closed enhancement (fixed)
build parallel for bjam and drake
| Reported by: | Kona8lend@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.2 |
| Keywords: | Cc: | jon.olsson@…, adfernandes (Andrew Fernandes), ruud@…, ryandesign (Ryan Carsten Schmidt), tvb377@… | |
| Port: | boost-jam boost mkvtoolnix |
Description
bjam (used by boost) and drake (used by mkvtoolnix) both benefit from parallel builds and luckily they both use compatible -jN args.
Attachments (2)
Change History (12)
comment:1 Changed 14 years ago by jmroot (Joshua Root)
| Cc: | jon.olsson@… adfernandes@… ruud@… added |
|---|---|
| Keywords: | bjam drake removed |
| Port: | boost-jam boost mkvtoolnix added |
Changed 14 years ago by Kona8lend@…
| Attachment: | parallel.patch added |
|---|
comment:3 Changed 14 years ago by adfernandes (Andrew Fernandes)
I patched boost in r75761.
Note that boost-jam and boost-build are independent of boost now; boost provides it's own built-in bjam tool that must be used to compile boost. (As far as I know, neither boost-jam or boost-build are supported by the boost development team, nor are they used by any other projects.)
comment:4 follow-up: 6 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|
comment:6 Changed 14 years ago by Kona8lend@…
Replying to ryandesign@…:
But boost's parallel build was deliberately turned off in r63389 because of the problems detailed in #23531. Have we verified that those problems no longer occur? If so, "use_parallel_build no" should be removed from the boost portfile too.
I am unable to reproduce what was detailed in #23531 but do regularly build boost -j8 with macports on 8-core box and it's never locked up. Mind you boost has progressed from 1.41 to 1.45 since 13 months ago, and xcode's bundled gcc has had some internal bumps as well.
Changed 14 years ago by Kona8lend@…
| Attachment: | boost_remove_use_parallel_build.patch added |
|---|
remove "use_parallel_build no"
comment:7 Changed 14 years ago by adfernandes (Andrew Fernandes)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Thanks for testing (and the patch!). Committed in r76350
I don't think we want to put code in base that is only used by one port. The portfiles can do whatever's appropriate with the build.jobs variable.