https://svn.boost.org/trac10/ticket/13560 <p> 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. </p> <p> 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. </p> <p> However, mpi Jamfile still refers to boost_python3 library which no longer exists. </p> <p> 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. </p> <p> I've proposed a patch to make mpi build against 'boost_python' without iterating for 2 3 major versions here </p> <p> <a class="ext-link" href="https://github.com/boostorg/mpi/pull/58/files"><span class="icon">​</span>https://github.com/boostorg/mpi/pull/58/files</a> </p> <p> Components are mpi&amp;python </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/13560 Trac 1.4.3