Bug 1670014

Summary:	binutils: Enable gold linker on all architectures with upstream implementation
Product:	Red Hat Enterprise Linux 7	Reporter:	Florian Weimer <fweimer>
Component:	binutils	Assignee:	Nick Clifton <nickc>
Status:	CLOSED ERRATA	QA Contact:	Miloš Prchlík <mprchlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.7	CC:	fweimer, law, mcermak, mprchlik, ohudlick
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	binutils-2.27-40.base.el7	Doc Type:	Enhancement
Doc Text:	Feature: The GOLD linker needs to be provided for the PowerPC64 and S390X architectures. Reason: These archiectures are supported on RHEL-7 and some packages require GOLD in order to link properly. Result: GOLD has now been enabled for all architectures supported by RHEL-7.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-06 12:41:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Florian Weimer 2019-01-28 12:08:29 UTC

Currently, ld.gold is missing on at least ppc64, ppc64le, s390x:

$ grep -Fc ld.gold binutils-2*.rpm
binutils-2.27-39.base.el7.aarch64.rpm:3
binutils-2.27-39.base.el7.i686.rpm:3
binutils-2.27-39.base.el7.ppc64le.rpm:0
binutils-2.27-39.base.el7.ppc64.rpm:0
binutils-2.27-39.base.el7.ppc.rpm:0
binutils-2.27-39.base.el7.s390.rpm:0
binutils-2.27-39.base.el7.s390x.rpm:0
binutils-2.27-39.base.el7.x86_64.rpm:3

I do not know the support status of ppc and s390, but we should enable the gold linker on all primary architectures.

Comment 2 Nick Clifton 2019-01-28 15:07:25 UTC

Fixed in binutils-2.27-40.base.el7

Comment 4 Miloš Prchlík 2019-06-20 08:06:27 UTC

Verified with binutils-2.27-41.base.el7 - ld.gold is present, no failed test case reported by gold binutils' upstream test suite.

Comment 6 errata-xmlrpc 2019-08-06 12:41:33 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.

https://access.redhat.com/errata/RHSA-2019:2075