[Boost-bugs] [Boost C++ Libraries] #13560: Cannot build --with-python --with-mpi --python-buildid=py36 python=3.6

Subject: [Boost-bugs] [Boost C++ Libraries] #13560: Cannot build --with-python --with-mpi --python-buildid=py36 python=3.6
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2018-05-03 11:43:37

#13560: Cannot build --with-python --with-mpi --python-buildid=py36 python=3.6
------------------------------------------+-----------------------------
 Reporter:  Dimitri John Ledkov <xnox@…>  |      Owner:  Matthias Troyer
     Type:  Bugs                          |     Status:  new
Milestone:  To Be Determined              |  Component:  mpi
  Version:  Boost 1.66.0                  |   Severity:  Problem
 Keywords:                                |
------------------------------------------+-----------------------------
 For a long time, debian would do multiple build configs of boost.
 First, build boost without python.
 Then build boost for each supported python version, including mpi/mpi-
 python/numpy.

 However, this does not appear to quite work. Previously boost_python
 introduced boost_python2 and boost_python3 libraries pointing at the
 default versions of respective major series. But in master/1.66/1.67 these
 appear to be gone.

 However, mpi Jamfile still refers to boost_python3 library which no longer
 exists.

 Either it is a bug in boost_python that it has dropped boost_python2 and
 boost_python3 aliases.
 Or it is a bug in mpi Jamfiles and it should stop using boost_python2 and
 boost_python3 aliases and simply compile against "boost_python" and use a
 matching buildid.

 I've proposed a patch to make mpi build against 'boost_python' without
 iterating for 2 3 major versions here

 https://github.com/boostorg/mpi/pull/58/files

 Components are mpi&python

-- 
Ticket URL: <https://svn.boost.org/trac10/ticket/13560>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.