Bug 1388682

Summary: chromium FTBFS on aarch64 epel7
Product: [Fedora] Fedora EPEL Reporter: D. Marlin <dmarlin>
Component: chromiumAssignee: Tom "spot" Callaway <spotrh>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel7CC: pbrobinson, yaneti
Target Milestone: ---   
Target Release: ---   
Hardware: aarch64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-01 21:51:54 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: 1371037    
Bug Blocks: 1285484    

Description D. Marlin 2016-10-25 21:49:07 UTC
Description of problem:

chromium fails to build from source for Fedora EPEL7 on RHELSA-7.2.


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

chromium-53.0.2785.143-1.el7


How reproducible:

consistently


Steps to Reproduce:
1.  On a RHELSA-7.2 host:
    mock -r epel-7-aarch64 chromium-53.0.2785.143-1.el7.src.rpm
2.
3.

Actual results:

Fails to build with the following error:

  Error: No Package found for libatomic


Expected results:

Not attempt to build for AArch64 (ExcludeArch).


Additional info:

libatomic is provided by gcc for most architectures, but support for libatomic is not included for AArch64 in gcc-4.8.  chromium should exclude arch 'aarch64' until support is included in gcc (est. 4.9).

Comment 1 Tom "spot" Callaway 2016-10-27 13:57:39 UTC
I'm pretty sure this goes deeper than libatomic. It is possible to get chromium building for arm/aarch64, but I would need time and shell access to the fastest possible aarch64 system to make the necessary changes. Chromium is not tiny. :/

Comment 2 D. Marlin 2016-10-27 20:04:31 UTC
Understood.  I checked the spec file, and it is already:
  ExclusiveArch:  x86_64 i686
so my request to exclude AArch64 is not needed.  Getting chromium to build on AArch64 is probably best handled in Fedora/Rawhide, which already has newer tools (and libatomic for AArch64).  Unfortunately, the fastest aarch64 systems today are in short supply, but I believe more/faster hardware will be available soon.  Perhaps we can revisit this then.

Comment 3 Fedora Admin user for bugzilla script actions 2020-06-03 02:48:02 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 4 Peter Robinson 2022-04-01 21:51:54 UTC
RHEL on aarch64 is EOL so closing