Re: Linking libboost_python.so to libpython

From: Jonathan Wakely (jwakely.boost_at_[hidden])
Date: 2020-04-03 17:11:44

On Fri, 3 Apr 2020 at 18:07, Peter Dimov via Boost <boost_at_[hidden]>
wrote:

> 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.
>

Right, but mpi.so doesn't appear to get built. Maybe it did, and is just
not where our build script expects it, I should check that.

>
> > 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.)
>

Ah, we also patch out the setting of rpaths, maybe we need to make that
happen in an additional place now. Thanks for the clues what to look at
next.

> What does user-config.jam contain?
>
>
import os ;
local RPM_OPT_FLAGS = [ os.environ RPM_OPT_FLAGS ] ;
local RPM_LD_FLAGS = [ os.environ RPM_LD_FLAGS ] ;
using gcc : : : <compileflags>$(RPM_OPT_FLAGS) <linkflags>$(RPM_LD_FLAGS) ;
using mpi ;
using python : 3.8 : /usr/bin/python3 : /usr/include/python3.8m : : : ;

> (Also... before spending too much time on this, consider trying 1.73 as
> well.)
>
>
I will, although I would be surprised if these problems have just gone away
by themselves, given that they seem to be related to downstream
customizations for Fedora, and so not reported upstream to Boost.