[pkg-boost-devel] Bug#734504: Bug#734504: libboost-python1.54-dev: shared library not linked against python

[Dimitri John Ledkov]

On 7 January 2014 18:46, Simon Richter <sjr at debian.org> wrote:
> Hi,
>
> On 07.01.2014 18:45, Dimitri John Ledkov wrote:
>
>>> /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/libboost_python.so: undefined reference to `PyList_Sort'
>
>>> It appears that the shared library is not linked against python.
>
>> Do you have a full build log & source-code/package available to inspect?
>
> Difficult -- it's the hg version of luxrays I was trying to build.
>
> The problem is fairly obvious though:
>
> $ nm -D /usr/lib/x86_64-linux-gnu/libboost_python.so | grep \ Py
>
> gives a set of undefined symbols that would be provided by libpython2.7
>
> $ nm -D /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 | grep \ Py
>
> but libboost_python.so is not linked against libpython2.7:
>

Yeah, it is interesting. In theory, compiled python extensions should
not link against libpythonX.Y, in practice libboost_python is not a
compiled extension, but rather c++/boost helper to create compiled
extensions, which again should not link against libpythonX.Y, and to
further mud things a given compiled extension can only be loaded by
matching magic-number ABI build of libpython at runtime (e.g. 2.7
non-optimised debug build of both).

Can you check if boost-python 1.53 and 1.49 linked against libpython ?

-- 
Regards,

Dimitri.