Bug 1323831 - seamonkey FTBFS on aarch64 epel7
Summary: seamonkey FTBFS on aarch64 epel7
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: seamonkey
Version: epel7
Hardware: aarch64
OS: Linux
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: epel7aarch64
TreeView+ depends on / blocked
Reported: 2016-04-04 21:26 UTC by D. Marlin
Modified: 2019-07-26 07:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed:
Type: Bug

Attachments (Terms of Use)

Description D. Marlin 2016-04-04 21:26:39 UTC
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):


How reproducible:


Steps to Reproduce:
1.  On a RHELSA-7.2 host:
    mock -r epel-7-aarch64 seamonkey-2.40-1.el7.src.rpm

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:
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):
this should probably be set up as ExclusiveArch in the spec file.

Comment 1 Dmitry Butskoy 2016-04-05 22:35:49 UTC
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...

Note You need to log in before you can comment on or make changes to this bug.