Opened 13 years ago
Closed 13 years ago
#3814 closed Bugs (fixed)
bjam special cases --pythonXXX options?
Reported by: | Owned by: | René Rivera | |
---|---|---|---|
Milestone: | Boost 1.42.0 | Component: | bjam |
Version: | Boost 1.41.0 | Severity: | Problem |
Keywords: | Cc: |
Description
The bjam shipped with Boost 1.41 generally ignores unrecognized options; e.g. "./bootstrap.sh; ./bjam --blabla" will build everything just fine. However, if I pass "--pythonbla", I get a very mysterious failure:
steve@riemann{boost}./bjam --pythonbla Boost.Build V2 Python port (experimental) /home/steve/Packages/boost/upstream/testing/trunk/boost/tools/build/v2/kernel/bootstrap.jam:223: in boost-build rule PYTHON_IMPORT_RULE unknown in module /home/steve/Packages/boost/upstream/testing/trunk/boost/boost-build.jam:17: in module scope
Why is this? This was not the behaviour in 1.40.
This breaks the "--pythonid" patch we use in Debian; c.f. https://svn.boost.org/trac/boost/ticket/3544
Note:
See TracTickets
for help on using tickets.
(In [58668]) Only use Python port of Boost.Build when exactly '--python' is passed. Fixes #3814.