gpaw config.py does not handle aarch64, causing the build to fail there. The following patch from rawhide fixes the build; please merge this into epel7 and f23 as well.
Created attachment 1105628 [details] Fix build on aarch64 (#1291383)
Commited in http://pkgs.fedoraproject.org/cgit/gpaw.git/commit/?id=9ea7340ac4a909b36eb015121c06877af5aa24ce Are those aarch64 builds performed at arm.koji.fedoraproject.org? Is there any cli? Can you verify if gpaw builds are fine now?
Scratch builds of -18 succeed on aarch64. Please build and update for Fedora and epel7.
I'm not familiar with this particular koji platform. What is "-18"? I've commited the change to Rawhide, Fedora 22/23, el6 and epel7, because I always try to keep the spec file in sync. Will a "standard" fedpkg update trigger also those aarch64 builds?
(In reply to marcindulak from comment #4) > I'm not familiar with this particular koji platform. What is "-18"? gpaw-0.11.0.13004-18 > I've commited the change to Rawhide, Fedora 22/23, el6 and epel7, > because I always try to keep the spec file in sync. > Will a "standard" fedpkg update trigger also those aarch64 builds? Yes.
gpaw-0.11.0.13004-18.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-6b7f39aa8e
gpaw-0.11.0.13004-18.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-c9c02fba95
gpaw-0.11.0.13004-18.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-606dd7afae
gpaw epel7 build fails now because CentOS started to build also on ppc64le and openblas is still missing there bug #1287105
gpaw-0.11.0.13004-18.el6 has been pushed to the Fedora EPEL 6 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-2016-6b7f39aa8e
gpaw-0.11.0.13004-18.fc22 has been pushed to the Fedora 22 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-2016-606dd7afae
gpaw-0.11.0.13004-18.fc23 has been pushed to the Fedora 23 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-2016-c9c02fba95
gpaw-0.11.0.13004-18.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
gpaw-0.11.0.13004-18.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
gpaw-0.11.0.13004-18.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
gpaw-0.11.0.13004-21.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-b736608e12
gpaw-0.11.0.13004-21.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-2016-b736608e12
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
gpaw-0.11.0.13004-21.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.