Opened 6 years ago
Last modified 6 years ago
#12515 new Bugs
bjam "python=X.X" option not recognized anymore
Reported by: | Owned by: | ||
---|---|---|---|
Milestone: | To Be Determined | Component: | Building Boost |
Version: | Boost 1.62.0 | Severity: | Problem |
Keywords: | Cc: |
Description
In Boost 1.62, specifying "python=3.5" is not working anymore: Always the first python entry in user-config.jam is selected. It seems to be related to a change in tools/build/src/tools/python.jam (line 905 ff), which appeared between 1.61.0 and 1.62.0.
Change History (4)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
I can confirm this. This regression is caused by
commit 2059618861eb25ae2ed3f1b6ebee8609365cbed9 Author: Rene Rivera <grafikrobot@gmail.com> Date: Sat Jul 16 15:53:30 2016 -0500
Reverting it fixes this problem. Another location for this patch is in development branch at,
https://github.com/boostorg/build/commit/78ffbe094400d277627b2c19ceb182d637b8baca
comment:3 by , 6 years ago
May this please be picked up at some time? Version 1.63 still contains this bug.
comment:4 by , 6 years ago
Here is similar bug report in GitHub issues: It no longer seems possible to build against both python2 and python3 #163
It also means that it makes it impossible (or at least hard for me) to build libboost_python and libboost_python3 at one run. While both files are present, in fact they are both python2 bindings.