Bug 1388682
Summary: | chromium FTBFS on aarch64 epel7 | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | D. Marlin <dmarlin> |
Component: | chromium | Assignee: | Tom "spot" Callaway <spotrh> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | epel7 | CC: | 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
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. :/ 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. This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component. RHEL on aarch64 is EOL so closing |