Ubuntu
oprofile package

opreport doesn't run: should link libbfd statically

Bug #179335 reported by Benjamin Redelings
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
oprofile (Debian)
Fix Released
Unknown
oprofile (Ubuntu)
Confirmed
Medium
Luca Falavigna

Bug Description

Binary package hint: oprofile

The opreport tool in oprofile does not run, because it dynamically links to libbdf-2.18.so although binutils only provides libbfd-2.18.20071027.so

This can be fixed by creating a symlink:
# ln -s libbfd-2.18.20071027.so libbfd-2.18.so

However, Debian fixed it by statically linking libbfd into oprofile, as described in Debian Bug #446360

-BenRI

Related branches

lp:ubuntu/karmic/oprofile
Luca Falavigna (dktrkranz)
Changed in oprofile:
assignee: nobody → dktrkranz
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package oprofile - 0.9.3-1.1ubuntu1

---------------
oprofile (0.9.3-1.1ubuntu1) hardy; urgency=low

  * Merge from debian unstable (LP: #179335), remaining changes:
    - Configuration file in /etc.
    - On powerpc configure --with-target=cell-be.
    - Fix for seg fault in opreport when using --xml and --details.
    - Change for opcontrol. Fix problem running on system using
      a network file system with different time base.
    - Change m4 file for SDK build process.
    - Add changes to allow profiling of code that the SPU runtime
      dynamically creates and runs on the stack.
  * debian/patches/opcontrol_bashisms:
    - fix bashisms in opcontrol script (LP: #172495)

oprofile (0.9.3-1.1) unstable; urgency=low

  * NMU
  * link libbfd static (closes: #446360)

 -- Luca Falavigna <email address hidden> Sat, 22 Dec 2007 09:53:22 +0000

Changed in oprofile:
status: Confirmed → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in oprofile:
status: Unknown → Fix Released
Revision history for this message
zecke (holger+launchpad) wrote :

This bug seems to be back in karmic. opreport is linking against a libbfd that is not available on my system (binutils-multiarch are installed, if that is relevant).

Revision history for this message
Al Dimond (businessmanprogrammersteve) wrote :

I'm seeing it on karmic also. As far as I can tell opreport should definitely be linked with this library statically. This mailing list conversation (http://<email address hidden>/msg631508.html) makes it sound like it's very easy to accidentally build a version that links dynamically.

Revision history for this message
Nelson Elhage (nelhage) wrote :

Reopening this, I'm seeing this problem bug in Karmic again as well.

[nelhage@phanatique:~]$ opreport
opreport: error while loading shared libraries: libbfd-2.19.91.20090910.so: cannot open shared object file: No such file or directory
[nelhage@phanatique:~]$ ls -l /usr/lib/libbfd*
-rw-r--r-- 1 root root 887K 2009-10-06 12:52 /usr/lib/libbfd-2.19.91.20091006.so
-rw-r--r-- 1 root root 6.2M 2009-10-06 12:52 /usr/lib/libbfd.a
lrwxrwxrwx 1 root root 26 2009-10-09 15:42 /usr/lib/libbfd.so -> libbfd-2.19.91.20091006.so

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

Other bug subscribers

Remote bug watches

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