Can't link to python_boost library due to multiarch changes

Bug #1217237 reported by Andreas Moog
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
boost1.53 (Ubuntu)
Fix Released
High
Dimitri John Ledkov

Bug Description

Hi there,

when boost1.53 got multiarched, all the libraries were moved to /usr/lib/<multi-arch-triplet>:

(saucy)andreas@incubator:~$ find /usr/lib -name libboost*
/usr/lib/x86_64-linux-gnu/libboost_python-py33.a
/usr/lib/x86_64-linux-gnu/libboost_python-py27.so.1.53.0
/usr/lib/x86_64-linux-gnu/libboost_python-py27.a
/usr/lib/x86_64-linux-gnu/libboost_python-py33.so.1.53.0
/usr/lib/x86_64-linux-gnu/libboost_python-py27.so
/usr/lib/x86_64-linux-gnu/libboost_python-py33.so

That works well for normal libraries, but the python one is a special case. As you can see, there are 2 libraries, one for python 2.7, one for 3.3. In the previous, non-multiarch, version, a symlink /usr/lib/libboost_python.so would be created to the default python version. Unfortunately the script didn't get adapted for the new location.

This breaks compilation of almost all programs that are linked against boost-python as well as auto-detection of boost for example in CMAKE: https://bugs.launchpad.net/bugs/1217106

Please see the attached patch for a possible solution. It sets the correct multi-arch location for the script during compilation and unbreaks CMAKE.

Revision history for this message
Andreas Moog (ampelbein) wrote :
Changed in boost1.53 (Ubuntu):
status: New → Confirmed
assignee: nobody → Dmitrijs Ledkovs (xnox)
Revision history for this message
Andreas Moog (ampelbein) wrote :

After a little talk on IRC, Dmitrijs proposed a different fix: Since the python2.7 release will be the latest in the 2.x series, the script that updates the symlink isn't necessary anymore and a static symlink can be used.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

But it seems like there wasn't anything in place to update the python3 -> python3.3 symlink.
Recently I've started to think that maybe the boost-python libraries should live in the multiarch & python abi-tag qualified locations e.g. same as libpython itself e.g. /usr/lib/pythonX.Y/confgi-X.Y$(abi-tag)-$(multiarch)/
I have implemented the static symlink in svn for debian, I need to do the boost uploads to fix this now.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

boost is currently blocked migrating due to Beta1 freeze, but this should reach saucy release pocket sometime on friday.

Changed in boost1.53 (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package boost1.53 - 1.53.0-6+exp3ubuntu4

---------------
boost1.53 (1.53.0-6+exp3ubuntu4) saucy; urgency=low

  * Rebuild to match boost-mpi-source version number.
 -- Dmitrijs Ledkovs <email address hidden> Tue, 03 Sep 2013 08:50:33 +0100

Changed in boost1.53 (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.