From: Peter Dimov (pdimov_at_[hidden])
Date: 2020-04-03 17:07:12
Jonathan Wakely wrote:
> Boost 1.70.0 and 1.71.0 fail to build with:
> ...updating 24 targets...
...
> ...updated 24 targets...
...
> + mv
> /builddir/build/BUILDROOT/boost-1.71.0-0.1.fc33.x86_64/usr/lib64/openmpi/lib/mpi.so
> /builddir/build/BUILDROOT/boost-1.71.0-0.1.fc33.x86_64/usr/lib64/python3.8/site-packages/openmpi/boost/
> mv: cannot stat
> '/builddir/build/BUILDROOT/boost-1.71.0-0.1.fc33.x86_64/usr/lib64/openmpi/lib/mpi.so':
> No such file or directory
This is not failure to build; the error comes from the script, it can't find
mpi.so.
> And 1.72.0 fails even earlier, with what looks like a conflict between
> building Boost.Serialization with "python" and "python-for-extensions"
> properties (if I'm reading python.jam right, which is unlikely):
...
> error: Name clash for
> '<p/builddir/build/BUILD/boost_1_72_0/stage/lib>libboost_serialization.so.1.72.0'
> error:
> error: Tried to build the target twice, with property sets having
> error: these incompatible properties:
> error:
> error: - none
> error: - <dll-path>/usr/lib <dll-path>/usr/lib/python3.8/config
I don't think this is a conflict between `python` and
`python-for-extensions`. Rather, it is a conflict between
libboost_serialization.so by itself (without rpath), and
libboost_serialization.so built as a dependency of libboost_mpi.so (for
which someone tries to set rpath.)
What does user-config.jam contain?
(Also... before spending too much time on this, consider trying 1.73 as
well.)