Bug 896624 - Firefox/Seamonkey fails to build on i586 on 13.1 and above
Firefox/Seamonkey fails to build on i586 on 13.1 and above
Status: RESOLVED FIXED
Classification: openSUSE
Product: openSUSE 13.1
Classification: openSUSE
Component: Firefox
Final
i586 Other
: P5 - None : Major (vote)
: ---
Assigned To: E-mail List
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-09-14 07:42 UTC by Wolfgang Rosenauer
Modified: 2021-09-07 12:23 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfgang Rosenauer 2014-09-14 07:42:01 UTC
Firefox 32 and Seamonkey 2.29 cannot do not build on 13.1 and above. Therefore this blocks further security updates for Seamonkey and forces us to ship Firefox ESR in the update channels for the moment.
https://build.opensuse.org/package/live_build_log/mozilla/firefox32/openSUSE_13.1/i586
https://build.opensuse.org/package/live_build_log/mozilla/seamonkey/openSUSE_13.1/i586

It seems to be toolchain dependent but I have no idea how to debug this further and need help.

I filed a bug upstream but apparently noone else has this issue so it probably won't get any traction:
https://bugzilla.mozilla.org/show_bug.cgi?id=1047803

CCing a few probably interested parties.
Comment 1 Sean Watson 2014-09-15 14:54:39 UTC
According to this http://forums.mozillazine.org/viewtopic.php?p=13727891#p13727891 Firefox 32+ has crossed the linker size limit for 32bit builds.

Does adding --enable-release fix the problem? Or as a last resort do --disable-optimize just for 32bit.
Comment 2 Wolfgang Rosenauer 2014-09-15 19:41:24 UTC
--enable-release does not fix it.
I will try --disable-optimize later but this would be quite ugly :-(
Comment 3 Wolfgang Rosenauer 2014-09-16 05:41:52 UTC
I can confirm that --disable-optimize fixes the issue with Firefox 33beta. So it most likely also would work for current stable 32 (and Seamonkey 2.29).

Since it's xpcshell which is crashing apparently here is a comparison of build flags between --disable-optimize on i586 and optimized on x86-64 of one exemplary CPP file: (we inject our optflags using C*FLAGS still via $RPM_OPT_FLAGS -Os -fno-strict-aliasing)
(-I stuff removed)

"unoptimized" i586 build (working):
[  751s] c++ -o XPCShellEnvironment.o -c -include /home/abuild/rpmbuild/BUILD/mozilla/config/gcc_hidden.h -DOS_POSIX=1 -DOS_LINUX=1 -DMOZ_GLUE_IN_PROGRAM -DMOZILLA_INTERNAL_API -DIMPL_LIBXUL  -DSTATIC_EXPORTABLE_JS_API -DNO_NSPR_10_SUPPORT -fPIC   -DMOZILLA_CLIENT -include ../../mozilla-config.h -MD -MP -MF .deps/XPCShellEnvironment.o.pp  -Wall -Wpointer-arith -Woverloaded-virtual -Werror=return-type -Werror=int-to-pointer-cast -Wtype-limits -Wempty-body -Wsign-compare -Wno-invalid-offsetof -Wcast-align -fomit-frame-pointer -fmessage-length=0 -grecord-gcc-switches -fstack-protector -O2 -Wall -D_FORTIFY_SOURCE=2 -funwind-tables -fasynchronous-unwind-tables -g -Os -fno-strict-aliasing -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -pipe  -DNDEBUG -DTRIMMED -g -fno-omit-frame-pointer       /home/abuild/rpmbuild/BUILD/mozilla/ipc/testshell/XPCShellEnvironment.cpp

"optimized" x86-64 build (working):
[ 1137s] c++ -o XPCShellEnvironment.o -c -include /home/abuild/rpmbuild/BUILD/mozilla/config/gcc_hidden.h -DOS_POSIX=1 -DOS_LINUX=1 -DMOZ_GLUE_IN_PROGRAM -DMOZILLA_INTERNAL_API -DIMPL_LIBXUL  -DSTATIC_EXPORTABLE_JS_API -DNO_NSPR_10_SUPPORT -fPIC   -DMOZILLA_CLIENT -include ../../mozilla-config.h -MD -MP -MF .deps/XPCShellEnvironment.o.pp  -Wall -Wpointer-arith -Woverloaded-virtual -Werror=return-type -Werror=int-to-pointer-cast -Wtype-limits -Wempty-body -Wsign-compare -Wno-invalid-offsetof -Wcast-align -fmessage-length=0 -grecord-gcc-switches -fstack-protector -O2 -Wall -D_FORTIFY_SOURCE=2 -funwind-tables -fasynchronous-unwind-tables -g -Os -fno-strict-aliasing -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -pipe  -DNDEBUG -DTRIMMED -g -Os -freorder-blocks  -fomit-frame-pointer      /home/abuild/rpmbuild/BUILD/mozilla/ipc/testshell/XPCShellEnvironment.cpp

I don't even see a real difference but I might miss the point.
Since it's not clear to me where it crashes exactly the above might also be a bad example. Probably we need to look at JS components?
Comment 4 Bernhard Wiedemann 2014-09-22 17:00:21 UTC
This is an autogenerated message for OBS integration:
This bug (896624) was mentioned in
https://build.opensuse.org/request/show/250744 Factory / seamonkey
https://build.opensuse.org/request/show/250745 13.1 / seamonkey
https://build.opensuse.org/request/show/250746 12.3 / seamonkey
Comment 5 Bernhard Wiedemann 2014-09-22 21:00:37 UTC
This is an autogenerated message for OBS integration:
This bug (896624) was mentioned in
https://build.opensuse.org/request/show/251469 Factory / MozillaFirefox
Comment 6 Swamp Workflow Management 2014-10-01 11:06:09 UTC
openSUSE-RU-2014:1263-1: An update that has one recommended fix can now be installed.

Category: recommended (moderate)
Bug References: 896624
CVE References: 
Sources used:
openSUSE 13.1 (src):    seamonkey-2.29-32.3
openSUSE 12.3 (src):    seamonkey-2.29-1.57.2
Comment 7 Swamp Workflow Management 2014-11-02 12:05:24 UTC
openSUSE-SU-2014:1344-1: An update that fixes 13 vulnerabilities is now available.

Category: security (moderate)
Bug References: 894370,896624,897890,900941,901213
CVE References: CVE-2014-1554,CVE-2014-1574,CVE-2014-1575,CVE-2014-1576,CVE-2014-1577,CVE-2014-1578,CVE-2014-1580,CVE-2014-1581,CVE-2014-1582,CVE-2014-1583,CVE-2014-1584,CVE-2014-1585,CVE-2014-1586
Sources used:
openSUSE 12.3 (src):    MozillaFirefox-33.0-1.90.1, mozilla-nspr-4.10.7-1.34.1, mozilla-nss-3.17.1-1.59.1, seamonkey-2.30-1.61.1
Comment 8 Swamp Workflow Management 2014-11-02 12:06:24 UTC
openSUSE-SU-2014:1345-1: An update that fixes 13 vulnerabilities is now available.

Category: security (moderate)
Bug References: 894370,896624,897890,900941,901213
CVE References: CVE-2014-1554,CVE-2014-1574,CVE-2014-1575,CVE-2014-1576,CVE-2014-1577,CVE-2014-1578,CVE-2014-1580,CVE-2014-1581,CVE-2014-1582,CVE-2014-1583,CVE-2014-1584,CVE-2014-1585,CVE-2014-1586
Sources used:
openSUSE 13.1 (src):    MozillaFirefox-33.0-46.2, mozilla-nspr-4.10.7-16.1, mozilla-nss-3.17.1-43.1, seamonkey-2.30-36.2
Comment 9 Wolfgang Rosenauer 2014-11-08 08:26:27 UTC
The problem is workarounded by using less optimization. So I'm closing this now.
Unfortunately having to use a bit less optimization brought us into the situation that starting with 13.2 (probably because of toolchain differences) brought us over the 32bit memory limit for the linker build stage.
Therefore Firefox 33.1 and seamonkey 2.30 do currently not build anymore on 13.2 and up. I'll open a new bug about it for tracking.
Comment 15 Swamp Workflow Management 2021-09-03 13:28:37 UTC
# maintenance_jira_update_notice
openSUSE-RU-2021:1220-1: An update that has one recommended fix can now be installed.

Category: recommended (moderate)
Bug References: 896624
CVE References: 
JIRA References: 
Sources used:
openSUSE Leap 15.2 (src):    seamonkey-2.53.8.1-lp152.3.16.1
Comment 16 Swamp Workflow Management 2021-09-07 01:16:33 UTC
# maintenance_jira_update_notice
openSUSE-RU-2021:1232-1: An update that has one recommended fix can now be installed.

Category: recommended (moderate)
Bug References: 896624
CVE References: 
JIRA References: 
Sources used:
openSUSE Backports SLE-15-SP2 (src):    seamonkey-2.53.8.1-bp152.4.9.1