Peter Dimov

As far as I can see, fixing this should be as easy as copying these two lines: https://github.com/boostorg/mpi/blob/develop/build/Jamfile.v2#L136-L137 to the corresponding place at https://github.com/boostorg/mpi/blob/develop/build/Jamfile.v2#L171 and then adding `PYTHON_EXTENSION` to the...

It's already cloned. https://github.com/boostorg/mpi/blob/develop/build/Jamfile.v2#L58-L74

In addition, the upstream version seems to do the same thing as these local overrides. What specifically do you want fixed?

Should be PYTHON_EXTENSION, not python-extension. Although if with the `if` removed it still doesn't apply, that's not the problem.

@SoapGentoo You're right, the superproject definition of `tag` needs `PYTHON_EXTENSION` added too for this to work.

Unrelated to this build problem, the addition of `mpi.so` to `boost-install` is questionable for other reasons; Boost should in all probability not be installing a file named `mpi.so` to `/usr/lib`...

I can fix this build issue by adding PYTHON_EXTENSION here: https://github.com/boostorg/boost/blob/master/boostcpp.jam#L188 and perhaps here for consistency: https://github.com/boostorg/boost/blob/master/boostcpp.jam#L226 However, this will likely break Boost.Python's examples such as this one: https://github.com/boostorg/python/blob/develop/example/quickstart/Jamfile#L15 which...

If `mpi.so` is indeed the correct name for the extension, the immediate fix here is to remove `mpi` from https://github.com/boostorg/mpi/blob/develop/build/Jamfile.v2#L173: ``` mpi_python_libs = boost_mpi_python ; ``` (The space before the...

Zero, not counting this one, which only became installable in 1.72 due to Andrey's change. This was actually reported to me as a bug in the 1.72 CMake config file...