Bug 1330711

Summary:	Build golang for AArch64 in RHEL7.3
Product:	Red Hat Enterprise Linux 7	Reporter:	Jon Masters <jcm>
Component:	golang	Assignee:	Jakub Čajka <jcajka>
Status:	CLOSED ERRATA	QA Contact:	Martin Cermak <mcermak>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	ddaney, jcm, jperrin, lsm5, mcermak, ohe, rrichter, yselkowi
Target Milestone:	rc	Keywords:	Extras
Target Release:	---
Hardware:	aarch64
OS:	Linux
Whiteboard:
Fixed In Version:	golang-1.6.2-1.el7	Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-04 01:35:43 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:
Bug Depends On:	1292956
Bug Blocks:	1250216, 1254407, 1268554, 1268561, 1270119, 1277314, 1285484, 1344553, 1344554, 1344590, 1344592, 1344593, 1344596, 1344598

Description Jon Masters 2016-04-26 18:30:49 UTC

Description of problem:

Current builds of golang are not including aarch64 support among the available hardware targets. An agreement has been reached internally that we will build golang for aarch64 in addition. This does not mean that we will build any of the other dependencies for Atomic Host or other layered Red Hat products.

Version-Release number of selected component (if applicable):

1.6-1.el7

How reproducible:

N/A

Steps to Reproduce:

1. N/A

Actual results:

The package is not built for aarch64

Expected results:

The package should be built for aarch64

Additional info:

Comment 2 Yaakov Selkowitz 2016-05-03 20:59:27 UTC

Is ppc64/ppc64le enablement being discussed as well?  Is there a separate bz for that or should this cover both?

Comment 4 Kevin Stansell 2016-05-17 16:00:14 UTC

*** Bug 1270119 has been marked as a duplicate of this bug. ***

Comment 5 huhuang 2016-05-26 18:44:30 UTC

*** Bug 1268554 has been marked as a duplicate of this bug. ***

Comment 8 errata-xmlrpc 2016-11-04 01:35:43 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://rhn.redhat.com/errata/RHBA-2016-2245.html