[Bug 1600391] Re: No b2 executable in libboost-tools-dev
Christopher Beck
1600391 at bugs.launchpad.net
Sun Sep 4 00:22:18 UTC 2016
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?
--
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