No b2 executable in libboost-tools-dev

Bug #1600391 reported by Christopher Beck
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
boost1.58 (Ubuntu)
Triaged
Wishlist
Unassigned
Xenial
Triaged
Wishlist
Unassigned
boost1.60 (Debian)
Fix Released
Unknown
boost1.60 (Ubuntu)
Triaged
Wishlist
Unassigned

Bug Description

The boost build tool, b2 is important for any project that is using the boost build system for its own purposes.

It is distributed in Ubuntu as part of the `libboost-tools-dev` package. However, it is renamed `bjam` there.

The `bjam` name is archaic. Something like five years ago, they decided to rename it to `b2` since it doesn't interoperate with the old perforce version `bjam` which isn't developed anymore.

http://stackoverflow.com/questions/5759434/boost-installation

http://www.boost.org/users/history/version_1_48_0.html

I understand that the ubuntu package still calls it `bjam` to avoid breakage (presumably), but can't it at least provide a symlink called `b2`? It seriously confused me for a long time why I couldn't get travis-ci to use `b2` after installing `libboost-all-dev`.

Jeremy Bícha (jbicha)
Changed in boost-defaults (Ubuntu):
importance: Undecided → Wishlist
status: New → Triaged
affects: boost-defaults (Ubuntu) → boost1.58 (Ubuntu)
Changed in boost1.60 (Ubuntu):
status: New → Triaged
importance: Undecided → Wishlist
no longer affects: boost1.60 (Ubuntu Xenial)
Changed in boost1.58 (Ubuntu Xenial):
importance: Undecided → Wishlist
status: New → Triaged
Changed in boost1.60 (Debian):
status: Unknown → New
Revision history for this message
Christopher Beck (cbeck88) wrote :

@Jeremy Bicha: Thank you for looking into this and researching it, your explanation of the problem and the link you found were much better than my original report.

Changed in boost1.60 (Debian):
status: New → Fix Released
Revision history for this message
Christopher Beck (cbeck88) wrote :

It looks like debian did not actually fixed this, they closed it because that package is now defunct. Is there anything I'm supposed to do to follow up on this? Should I file it again against a different version of debian boost package?

Revision history for this message
dino99 (9d9) wrote :

@Christopher

as per the Debian comments (1.60 has been dropped, and its associated bugs too; considering 1.60 as a transitional version), you might check their now only valid 1.61 release.

If 1.61 is still having the problem you have reported here, then report against it with a new debbugs report and a launchpad one.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.