Bug 748927 - SystemTap affected by ".stapsdt.base.1"
Summary: SystemTap affected by ".stapsdt.base.1"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: binutils
Version: 5.7
Hardware: All
OS: Linux
high
low
Target Milestone: rc
: 5.8
Assignee: Andreas Schwab
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On: 711924
Blocks: 758797
TreeView+ depends on / blocked
 
Reported: 2011-10-25 15:26 UTC by Jan Kratochvil
Modified: 2013-07-23 07:56 UTC (History)
10 users (show)

Fixed In Version: binutils-2.17.50.0.6-19.el5
Doc Type: Bug Fix
Doc Text:
Clone Of: 711924
Environment:
Last Closed: 2012-02-21 06:39:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0271 0 normal SHIPPED_LIVE binutils bug fix update 2012-02-20 15:06:19 UTC

Comment 1 RHEL Program Management 2011-10-25 15:27:54 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 18 Jan Kratochvil 2011-12-01 15:34:17 UTC
glibc-2.5-75 has the line
%define systemtaparches %{ix86} x86_64 ppc ppc64 s390 s390x

from RHEL-6 but for RHEL-5 there must be also ia64:
%define systemtaparches %{ix86} x86_64 ppc ppc64 s390 s390x ia64

Comment 19 Michal Nowak 2011-12-01 15:50:45 UTC
Do you speak about glibc.spec file? Because there's the 'systemtaparches' definition, not in binutils.spec.

Comment 20 Jan Kratochvil 2011-12-01 16:06:57 UTC
Thanks for the notice, yes, moving FailedQA to glibc Bug 711924, my fault.

Comment 22 errata-xmlrpc 2012-02-21 06:39:38 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0271.html


Note You need to log in before you can comment on or make changes to this bug.