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.
|Summary:||seamonkey: Does not support aarch64 in f19 and rawhide|
|Product:||[Fedora] Fedora||Reporter:||Dennis Gilmore <dennis>|
|Component:||seamonkey||Assignee:||Martin Stransky <stransky>|
|Status:||CLOSED EOL||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||23||CC:||caillon+fedoraproject, dennis, dmitry, gecko-bugs-nobody, kengert, stransky|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2016-12-20 12:37:27 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:|
Description Dennis Gilmore 2013-03-23 16:18:36 UTC
Support for the ARM 64 bit CPU architecture (aarch64) was introduced in autoconf 2.69. seamonkey appears to use an earlier version of autoconf, preventing its being built. This can be fixed in of three ways (In order of preference): 1. Work with upstream to migrate the package to autoconf 2.69. 2. Rerun autoconf or autoreconf in %prep or %build prior to running configure. 3. Apply the patch at http://ausil.fedorapeople.org/aarch64/seamonkey/seamonkey-aarch64.patch which updates config.guess and config.sub to recognize aarch64.
Comment 1 Martin Stransky 2013-10-15 14:44:56 UTC
I wonder if Firefox/Xulrunner has the same problem or not? Because I don't see such report for Firefox.
Comment 2 Dmitry Butskoy 2013-11-07 19:22:28 UTC
The patch is against seamonkey-2.16, whereas newer seamonkey-2.21 was successfully build for armv7hl for f20 and rawhide, see: http://kojipkgs.fedoraproject.org//packages/seamonkey/2.21/1.fc21/armv7hl/seamonkey-2.21-1.fc21.armv7hl.rpm http://kojipkgs.fedoraproject.org//packages/seamonkey/2.21/1.fc20/armv7hl/seamonkey-2.21-1.fc20.armv7hl.rpm
Comment 3 Dennis Gilmore 2014-06-23 15:43:15 UTC
this is 64 bit arm not 32 bit there is not a aarch64 build
Comment 4 Jan Kurik 2015-07-15 14:48:59 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
Comment 5 Fedora End Of Life 2016-11-24 10:58:14 UTC
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Comment 6 Fedora End Of Life 2016-12-20 12:37:27 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.