This bug was fixed in the package oprofile - 0.9.4+cvs20090629-2ubuntu1
---
oprofile (0.9.4+cvs20090629-2ubuntu1) karmic; urgency=low
* Merge from debian unstable (LP: #392346), remaining changes:
- debian/control:
+ Add LPIA architecture.
+ Build-depend on autoconf,
Solution is to compile oprofile every time libc is upgraded.
It would nice of course that opreport&oprof_start would both use
libbfd.so symlink instead of so directly. I don't know why it isn't done
that way
--
oprofile-gui fails to start (missing libbfd)
https://bugs.launchpad.net/bugs/322074
Y
Same for me (oprofile-gui 0.9.3-1.1ubuntu2).
uname -a: Linux booxter-laptop 2.6.27-14-generic #1 SMP Fri Mar 13 19:54:51 UTC
2009 x86_64 GNU/Linux
boox...@booxter-laptop:~$ oprof_start
oprof_start: error while loading shared libraries: libbfd-2.18.0.20080103.so:
cannot open shared object file:
I ran into the same problem.
--
oprofile-gui fails to start (missing libbfd)
https://bugs.launchpad.net/bugs/322074
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
I get:
w...@wolf-desktop:~$ opreport
opreport: error while loading shared libraries: libbfd-2.19.so: cannot open
shared object file: No such file or directory
/usr/lib/libbfd-2.19.1.so exists, providing a symbolic link named
"libbfd-2.19.so" to it made opreport work.
oprofile 0.9.3-2ubuntu1
binu
