Re: Bug#887494: mozjs52: FTBFS on sparc64: interpreter segfaults
On 01/17/2018 01:33 PM, Simon McVittie wrote: If there are patches for sparc64 in firefox-esr or in upstream Firefox, they are probably also applicable to mozjs52. There are, please see [1]. As you can see from [2], my patches were all merged for Firefox 53 and therefore are not present in mozjs52. I can whip up a patch for mozjs52 to add sparc64 support if there is a realistic chance for it to be merged. My m68k [3] and sh4 [4] patches for mozjs52 are still without any reply, for example. Generally, getting mozjs52 to build on most platforms is easy and I can help with that. Adrian [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824449#73 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1275204 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880693 [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880692 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#887494: mozjs52: FTBFS on sparc64: interpreter segfaults
Source: mozjs52
Version: 52.3.1-7
Severity: normal
mozjs52 runs a smoke-test on the js sample interpreter (which is no longer
installed, but is still built) to check whether the built binaries are
in any way functional. On sparc64, the answer is that they are not:
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> SRCDIR=/<>/js/src DEB_HOST_ARCH=sparc64
> /<>/debian/test.sh
> Segmentation fault
> Smoke-test failed: did interpreter initialization fail? (see #873778)
> debian/rules:99: recipe for target 'override_dh_auto_test' failed
The failing command is:
"$SRCDIR/js/src/js" -e 'print("Hello, world")'
so this probably indicates that sparc64 builds of mozjs are unable to
interpret JavaScript at all.
This appears to be a regression since mozjs24, which passed at least some
of its build-time tests on sparc64. Maybe mozjs52 is making assumptions
about the layout of virtual memory that are not true on sparc64?
If there are patches for sparc64 in firefox-esr or in upstream Firefox,
they are probably also applicable to mozjs52.
Regards,
smcv
