*** This bug is a duplicate of bug 426614 ***
https://bugs.launchpad.net/bugs/426614
** This bug has been marked a duplicate of bug 426614
oprofile is linked against non-shipping version of libbfd
--
opreport doesn't run: should link libbfd statically
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://www.mail-archive.com/debian-bugs-
d...@lists.debian.org/msg631508.html) makes it sound like it's very easy
to accidentally build a version
Reopening this, I'm seeing this problem bug in Karmic again as well.
[nelh...@phanatique:~]$ opreport
opreport: error while loading shared libraries: libbfd-2.19.91.20090910.so:
cannot open shared object file: No such file or directory
[nelh...@phanatique:~]$ ls -l /usr/lib/libbfd*
-rw-r--r-- 1
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).
--
opreport doesn't run: should link libbfd statically
https://bugs.launchpad.net/bugs/179335
You received this bug notification
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).
--
opreport doesn't run: should link libbfd statically
https://bugs.launchpad.net/bugs/179335
You received this bug notification
