Description of problem: seamonkey-2.40-1.el7 fails to build from source for Fedora EPEL7 on RHELSA-7.2. Version-Release number of selected component (if applicable): seamonkey-2.40-1.el7 How reproducible: consistently Steps to Reproduce: 1. On a RHELSA-7.2 host: mock -r epel-7-aarch64 seamonkey-2.40-1.el7.src.rpm 2. 3. Actual results: Fails to build with the following error: /builddir/build/BUILD/seamonkey-2.40/seamonkey-2.40/mozilla/media/webrtc/trunk/build/build_config.h:160:2: error: #error Please add support for your architecture in build/build_config.h #error Please add support for your architecture in build/build_config.h Expected results: builds without errors. Additional info: The previous version (2.39-2.el7) built without errors for Fedora EPEL7 on RHELSA-7.2. It also built for Fedora EPEL7 on ppc64le: http://koji.fedoraproject.org/koji/buildinfo?buildID=712420 however according to the 2.40-1.el7 changelog: - avoid ppc64le builds as well (#866589) BZ#866589 was very old (2012-10-15) and for EPEL6, not EPEL7. I'm not sure if the failure to build on AArch64 is related to the change that disabled ppc64le, but if seamonkey is now to be x86_64 only (only arch built): http://koji.fedoraproject.org/koji/buildinfo?buildID=745448 this should probably be set up as ExclusiveArch in the spec file.
We build for i686 and x86_64 only. Other arches disabled due to missing real hardware to check on, and missing active users on those arches. Besides that, I'm not sure whether it is useful to build it on mostly "server-oriented arches" (like ppc64). ExclusiveArch would be incorrect, since the code in general is not x86-only, we just cannot love it enough on other arches. OTOH it is an easiest way to solve the issue...