On Wed, Apr 02, 2008 at 02:21:17PM +0200, Sune Vuorela wrote: > Justification: packaging on crack
That's a little harsh considering the limited analysis you presented.
> Looking at the newer boost-python-dev packages, I see tihs:
>
> $ dpkg -L libboost-python-dev | grep /usr/lib
[ ... ]
> Now - anything that tries linking with -lpython_boost or
> -lpython_boost-mt fails.
I'm assuming you really meant -lboost_python and -lboost_python-mt
> Why aren't there default python symlinks ?
There are default symlinks. You won't see them in "dpkg -L" output
because they are created by the postinst script, depending on which
python you have installed. You should see something like:
/usr/lib/libboost_python-mt.so -> libboost_python-mt-py24.so
/usr/lib/libboost_python.so -> libboost_python-py24.so
What is output of
dpkg l python
ls -l /usr/lib/libboost_python{,-mt}.so
If the latter doesn't show the symlinks, run
sudo /usr/share/python/runtime.d/libboost-python-dev.rtupdate rtupdate
none python2.4
ls -l /usr/lib/libboost_python{,-mt}.so
If there are no symlinks at install time, then please help me to
understand what went wrong. There was a bug in the -8 and -9 versions
in that boost-python-dev failed to install if no python was installed
(#473607). This is fixed in -10.
However, -10 has a bug in that you can install libboost-python-dev
without python and get no compatibility scripts. I had thought that
the subsequent install of python would run the rtupdate script and
create the symlinks, but that does not seem be the case. If this is
your situation, you can work around it by invoking rtupdate as shown
above.
Please let me know what sequence of package installs (and what version
of libboost-python-dev) led to the situation of no symlinks.
Thanks,
-Steve
signature.asc
Description: Digital signature
