opreport doesn't run: should link libbfd statically
Bug #179335 reported by
Benjamin Redelings
This bug report is a duplicate of:
Bug #426614: oprofile should not link libbfd dynamically.
Edit
Remove
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-
This can be fixed by creating a symlink:
# ln -s libbfd-
However, Debian fixed it by statically linking libbfd into oprofile, as described in Debian Bug #446360
-BenRI
Related branches
Changed in oprofile: | |
assignee: | nobody → dktrkranz |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in oprofile: | |
status: | Unknown → Fix Released |
To post a comment you must log in.
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: target= cell-be. patches/ opcontrol_ bashisms:
- Configuration file in /etc.
- On powerpc configure --with-
- 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/
- 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