Synced.
** Changed in: sysprof (Ubuntu)
Status: Fix Committed = Fix Released
--
Sysprof cannot run, looking for wrong libbfd
https://bugs.launchpad.net/bugs/46224
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
This is fixed in debian an will be fixed with next sync (see bug
#186158)
** Changed in: sysprof (Ubuntu)
Status: Triaged = Fix Committed
--
Sysprof cannot run, looking for wrong libbfd
https://bugs.launchpad.net/bugs/46224
You received this bug notification because you are a member of
** Changed in: sysprof (Debian)
Status: Confirmed = Fix Released
--
Sysprof cannot run, looking for wrong libbfd
https://bugs.launchpad.net/bugs/46224
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Please don't upload/sponsor the debdiff:
It's been fixed in Debian now, too. See the sync request at bug 186158.
--
Sysprof cannot run, looking for wrong libbfd
https://bugs.launchpad.net/bugs/46224
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
** Changed in: sysprof (Debian)
Status: Unknown = Confirmed
--
Sysprof cannot run, looking for wrong libbfd
https://bugs.launchpad.net/bugs/46224
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
I've contacted upstream (Soeren Sandmann) about this and he definitely
recommends statically linking against libbfd and says additionally:
I think bfd using apps in general should do that. On Fedora,
-lbfd does that by default, so I'd suggest doing the same on
Ubuntu/Debian.
Since this is not a
Broken again in Hardy.
** Changed in: sysprof (Ubuntu)
Assignee: (unassigned) = Daniel Hahler (blueyed)
Status: Fix Released = In Progress
** Bug watch added: Debian Bug tracker #439272
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=439272
** Also affects: sysprof (Debian) via
The proposed patch fixes this once and for all by linking statically against
libbfd.
I have not tested, if this causes other failures once the versions of libbfd
are different on the system from the version sysprof has been linked against!
The patch is taken from the Debian bug.
The debdiff
** Attachment removed: debdiff for Hardy
http://launchpadlibrarian.net/11516361/sysprof_1.0.9-1ubuntu1.dsc.diff
** Attachment added: debdiff for hardy
http://launchpadlibrarian.net/11516453/sysprof_1.0.9-1ubuntu1.dsc.diff
--
Sysprof cannot run, looking for wrong libbfd
Aaand it's broken again.
** Changed in: sysprof (Ubuntu)
Status: Fix Released = Confirmed
--
Sysprof cannot run, looking for wrong libbfd
https://bugs.launchpad.net/bugs/46224
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
sysprof (1.0.8-3build1) gutsy; urgency=low
* Rebuild for recent libbfd (from binutils) (LP: #46224).
-- Michael Bienia [EMAIL PROTECTED] Wed, 29 Aug 2007 17:48:55 +0200
** Changed in: sysprof (Ubuntu)
Status: Confirmed = Fix Released
--
Sysprof cannot run, looking for wrong libbfd
sysprof needs to be rebuild everytime a new version of binutils gets
uploaded.
sysprof is currently in sync with binutils in gutsy.
** Changed in: sysprof (Ubuntu)
Status: Confirmed = Fix Released
--
Sysprof cannot run, looking for wrong libbfd
https://bugs.launchpad.net/bugs/46224
You
To quote the description of binutils-dev (from which the libbfd in
question comes):
Note that building Debian packages which depend on the shared libbfd is
Not Allowed.
So it looks like sysprof is doing something naughty here.
--
Sysprof cannot run, looking for wrong libbfd
And again in gutsy:
sysprof: error while loading shared libraries:
libbfd-2.17.50.20070426.so: cannot open shared object file: No such file
or directory
--
Sysprof cannot run, looking for wrong libbfd
https://bugs.launchpad.net/bugs/46224
You received this bug notification because you are a
14 matches
Mail list logo
