Bug 748927

Summary:	SystemTap affected by ".stapsdt.base.1"
Product:	Red Hat Enterprise Linux 5	Reporter:	Jan Kratochvil <jan.kratochvil>
Component:	binutils	Assignee:	Andreas Schwab <schwab>
Status:	CLOSED ERRATA	QA Contact:	qe-baseos-tools-bugs
Severity:	low	Docs Contact:
Priority:	high
Version:	5.7	CC:	bgollahe, fche, jan.kratochvil, jkurik, law, mfranc, mnowak, nobody+bgollahe, patrickm, pmuller
Target Milestone:	rc
Target Release:	5.8
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	binutils-2.17.50.0.6-19.el5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	711924	Environment:
Last Closed:	2012-02-21 06:39:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	711924
Bug Blocks:	758797

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