registry team mailing list archive
-
registry team
-
Mailing list archive
-
Message #14484
[Bug 588033] Re: oprofile should not link libbfd dynamically, again [oprofile needs rebuilding against binutils 2.20.51.20100710]
Bug auto-closing is currently broken:
oprofile (0.9.6-1.1ubuntu1) maverick; urgency=low
.
* Merge from debian unstable. Remaining changes:
- Split out libopagent1 runtime library.
- debian/oprofile.postinst: Really really make it work this time by
adding the oprofile:oprofile system user and group as required for
JIT support (see README_PACKAGERS)
- Add documentation about vmlinux / linux-image-debug.ddeb.
- debian/patches/arm-factor-out-armv7-common-architectural-events,
debian/patches/arm-correct-usage-of-core-technology-for-v7-and-mpcore,
debian/patches/arm-add-support-for-cortex-a9-events:
ARMv7 cleanup and Cortex-A9 support, backported from
http://article.gmane.org/gmane.linux.oprofile/8563.
* Statically link libbfd. (LP: #588033)
.
oprofile (0.9.6-1.1) unstable; urgency=low
.
* Non-maintainer upload.
* Add patch by Yukiharu YABUKI to staticaly link against libbfd
(Closes: #537744, #573905)
** Changed in: oprofile (Ubuntu)
Importance: Undecided => Medium
** Changed in: oprofile (Ubuntu)
Status: Confirmed => Fix Released
--
oprofile should not link libbfd dynamically, again [oprofile needs rebuilding against binutils 2.20.51.20100710]
https://bugs.launchpad.net/bugs/588033
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.