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 1035485 - seamonkey failed to build on armv7hl
Summary: seamonkey failed to build on armv7hl
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: seamonkey
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dmitry Butskoy
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F-ExcludeArch-ARM
TreeView+ depends on / blocked
 
Reported: 2013-11-27 21:44 UTC by Dmitry Butskoy
Modified: 2020-05-01 17:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 10:39:02 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Dmitry Butskoy 2013-11-27 21:44:23 UTC 
Seamonkey-2.22 fails to build on armv7hl.

The error report is:
> /usr/bin/ld: failed to set dynamic section sizes: Memory exhausted
which probably is inspired by not enough memory on the Fedora ARM build environment.

The previous version (2.21) was built fine, the correspond Firefox-25 is fine too.
Since the Seamonkey is bigger than Firefox, its build requires more memory on the build machine. (Since 2.21 was built OK, perhaps a little bit more memory).

Since ARM is a new arch for Fedora now, and the Firefox browser is provided for armv7hl anyway, it is better to not provide armv7hl build for now.
Comment 1 Peter Robinson 2014-06-10 19:48:06 UTC 
Closing as it's long been built as xulrunner supports ARMv7hl
Comment 2 Dmitry Butskoy 2014-06-10 21:23:47 UTC 
No, just a first attempt to build was OK (probably occasionally).

Then, newer versions was failed to build because of not enough memory on the ARM build machine
(seamonkey build requires more than 4Gb, else it fails at ld linkage stage).

Currently, armv7hl is excluded in spec file.
Comment 3 Peter Robinson 2014-06-10 22:49:13 UTC 
(In reply to Dmitry Butskoy from comment #2)
> No, just a first attempt to build was OK (probably occasionally).
> 
> Then, newer versions was failed to build because of not enough memory on the
> ARM build machine
> (seamonkey build requires more than 4Gb, else it fails at ld linkage stage).

In firefox/xulrunner the following is used and it massively reduces memory usage and we don't get failures. 

%ifarch s390 %{arm} ppc aarch64                                         
MOZ_LINK_FLAGS="-Wl,--no-keep-memory -Wl,--reduce-memory-overheads"
%endif

> Currently, armv7hl is excluded in spec file.

Sorry, could have sworn I saw armv7hl builds
Comment 4 Dmitry Butskoy 2014-06-10 23:37:47 UTC 
> I saw armv7hl builds
It is possible that just one build is present somewhere...

Anyway, we lack any testers for seamonkey at armv7hl (not too many users at all even for x86/x86_64), hence it would be better to exclude it for now.
Comment 5 Jaroslav Reznik 2015-03-03 15:14:30 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 6 Fedora End Of Life 2016-07-19 10:39:02 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.
Comment 7 Fedora End Of Life 2017-07-25 18:36:35 UTC 
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 8 Jan Kurik 2017-08-15 08:43:41 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.
Comment 9 Ben Cotton 2018-11-27 13:52:05 UTC 
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 10 Ben Cotton 2019-02-19 17:12:06 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle.
Changing version to '30.
Comment 11 Ben Cotton 2020-04-30 22:11:05 UTC 
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 '30'.

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 30 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.
Note You need to log in before you can comment on or make changes to this bug.