Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1460813
Summary: | chromium not part of aarch64 package repo. | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jeremy Linton <jeremy.linton> | ||||||
Component: | chromium | Assignee: | Tom "spot" Callaway <tcallawa> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 26 | CC: | rblakley, tcallawa, yaneti | ||||||
Target Milestone: | --- | Keywords: | Reopened | ||||||
Target Release: | --- | ||||||||
Hardware: | aarch64 | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | chromium-60.0.3112.113-1.fc26 chromium-60.0.3112.113-1.fc25 chromium-60.0.3112.113-2.el7 | Doc Type: | If docs needed, set a value | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2017-09-02 22:25:02 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: | |||||||||
Bug Blocks: | 245418 | ||||||||
Attachments: |
|
Description
Jeremy Linton
2017-06-12 20:30:14 UTC
If you succeed in building it there with nacl/pnacl disabled, let me know, I'm happy to apply patches to enable that arch. It didn't get very far until it died trying to find the aarch64 compiler, which is odd because i'm not trying to cross compile it. I hacked it up a bit, and it is running again. It's not disabled because I have any prejudice against other arches. Chromium is a bear to build. :) I was able to successfully build and install chromium-60.0.3112.90 on a Fedora 26 aarch64 system, I'll attach the patches below that I used. Hopefully they help get chromium in the Fedora aarch64 repos. Created attachment 1314983 [details]
ffmpeg patch to allow aarch64 to successfully build
Created attachment 1314984 [details]
Patch for the spec file to enable aarch64 to compile.
Two comments, first I don't think you need to modify the depot_tools files, as adding a BuildRequires and using the system ninja is sufficient (I can attach a patch for that). I actually got it compiling a month or so ago with a similar change (target_cpu="", with a BUILD.gn) change, but got stuck modifying clean_ffmpeg.sh to add all the appropriate aarch64 files because the turnaround time discovering missing files was hours long the way I was doing it. Anyway, I built an "unclean" version with my ninja change, and the attached ffmpeg change here: https://koji.fedoraproject.org/koji/taskinfo?taskID=21444120 I thought that one was going to have armv7 as well, but it seems I didn't get the arch exclusion right for armv7. (In reply to Jeremy Linton from comment #7) > Two comments, first I don't think you need to modify the depot_tools files, > as adding a BuildRequires and using the system ninja is sufficient (I can > attach a patch for that). I actually got it compiling a month or so ago with > a similar change (target_cpu="", with a BUILD.gn) change, but got stuck > modifying clean_ffmpeg.sh to add all the appropriate aarch64 files because > the turnaround time discovering missing files was hours long the way I was > doing it. > > Anyway, I built an "unclean" version with my ninja change, and the attached > ffmpeg change here: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=21444120 > > I thought that one was going to have armv7 as well, but it seems I didn't > get the arch exclusion right for armv7. Yeah I modified the depot_tools file because it was cleaner looking than having to add in more ifarch aarch64 for every ninja line. But that was just my preference, whichever works to get aarch64 support added works for me :), the depot_tools file probably needs to be modified upstream to prevent this issue though. For armv7, the arch reference is armv7hl if I remember correctly, I may be incorrect though. I merged Ryan's change and it is now building for aarch64 properly, once I got some source issues resolved. If either of you wants to change things up, feel free to throw a pull request at me. :) chromium-60.0.3112.113-2.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-8f80d01c29 chromium-60.0.3112.113-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-e11dade5d0 chromium-60.0.3112.113-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-c708c044e3 chromium-60.0.3112.113-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. chromium-60.0.3112.113-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report. chromium-60.0.3112.113-2.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report. |