[Bug 1600391] Re: No b2 executable in libboost-tools-dev

dino99 1600391 at bugs.launchpad.net
Sun Sep 4 02:33:43 UTC 2016


@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.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to boost1.60 in Ubuntu.
https://bugs.launchpad.net/bugs/1600391

Title:
  No b2 executable in libboost-tools-dev

Status in boost1.58 package in Ubuntu:
  Triaged
Status in boost1.60 package in Ubuntu:
  Triaged
Status in boost1.58 source package in Xenial:
  Triaged
Status in boost1.60 package in Debian:
  Fix Released

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`.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boost1.58/+bug/1600391/+subscriptions



More information about the foundations-bugs mailing list