GNOME 3.30 stabilization will proceed within a couple of days, and stable spidermonkey:60 is a hard pre-requisite for that as the newer 3.30 required dev-libs/gjs version has upgraded to it (from spidermonkey:38; gjs versions using :45 were never stable targets). Please CC arches if fine; we need at least "alpha amd64 arm ia64 ppc ppc64 sparc x86".
[02:12:41] <@Anarchy> leio, ack cc the archs you want for spidermonkey:60 I'm not sure what's going on with sparc; it has stable keywords on gjs, but no stable spidermonkey anymore.
amd64 stable
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=eb7de78e42fc8c14e2ed9fcf3b071c63aa1c6a8d commit eb7de78e42fc8c14e2ed9fcf3b071c63aa1c6a8d Author: Tobias Klausmann <klausman@gentoo.org> AuthorDate: 2019-05-08 14:37:34 +0000 Commit: Tobias Klausmann <klausman@gentoo.org> CommitDate: 2019-05-08 14:37:46 +0000 dev-lang/spidermonkey-60.5.2_p0-r2: alpha stable Bug: http://bugs.gentoo.org/685150 Signed-off-by: Tobias Klausmann <klausman@gentoo.org> dev-lang/spidermonkey/spidermonkey-60.5.2_p0-r2.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sparc stable
x86 stable
(In reply to Mikle Kolyada from comment #5) > x86 stable hmm, not really
arm stable
(In reply to Mikle Kolyada from comment #8) > arm stable not really, at least USE="-jit" is broken.
USE=jit needs to be package.use.mask'd and only unmasked on a few platforms. It's broken on alpha, ppc, ppc64 as well.
And it should be force on for arm, here it's the other way around :)
Adding hppa since stabilisation of 52.9.1_pre1 timed out in bug 661470, and we surely want to cleanup old spidermonkey at some point. hppa revdeps: net-libs/libproxy[spidermonkey], www-client/elinks[javascript]
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=39f0eafc3d0ca0f5993d8e6a5b1334ba7e4408da commit 39f0eafc3d0ca0f5993d8e6a5b1334ba7e4408da Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2019-06-21 02:25:15 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2019-06-21 02:27:02 +0000 profiles: Mask/unmask spidermonkey[jit] per-platform USE=jit fails to build on most platforms, but does build on x86, amd64, and arm. Bug: https://bugs.gentoo.org/685150 Signed-off-by: Matt Turner <mattst88@gentoo.org> profiles/arch/amd64/package.use.mask | 5 +++++ profiles/arch/arm/package.use.mask | 5 +++++ profiles/arch/base/package.use.mask | 4 ++++ profiles/arch/x86/package.use.mask | 5 +++++ 4 files changed, 19 insertions(+)
ppc/ppc64 stable
hppa stable
ia64 stable
s390 stable
(In reply to Matt Turner from comment #16) > ia64 stable How did you get it? sm60 simply fails to initialize JS, leading to bug #701052 and bug #701054, thus blocking bug #685254. Even worse, while js38 correctly starts up the JS interpreter js> build() built on Nov 21 2017 at 12:50:26 js> quit() js60 gives absolutely nothing! In fact, I fear that the JS interpreter isn't started at all. I doesn't seem to crash either, but I'm unable to rebuild dev-lang/spidermonkey:60 with debugging symbols to double-check with GDB, as =sys-auth/polkit-0.116-r1 installed on my system has a strong dev-lang/spidermonkey:60[-debug] dependency. Can you please check that your js60 binary correctly starts up the JS interpreter on your ia64 install? Thanks, Émeric
(In reply to Émeric Maschino from comment #18) > (In reply to Matt Turner from comment #16) > > ia64 stable > > How did you get it? sm60 simply fails to initialize JS, leading to bug > #701052 and bug #701054, thus blocking bug #685254. It's been a while, but IIRC the test suite for polkit passed on ia64 with spidermonkey:60.
(In reply to Matt Turner from comment #19) > > It's been a while, but IIRC the test suite for polkit passed on ia64 with > spidermonkey:60. Do you still have access to this ia64 install? Can you please check what happens when you fire up js60 in a command-line prompt?
(In reply to Émeric Maschino from comment #18) > Can you please check that your js60 binary correctly starts up the JS > interpreter on your ia64 install? Yeah, looks like 'js60' just returns 1.
(In reply to Matt Turner from comment #21) > (In reply to Émeric Maschino from comment #18) > > Can you please check that your js60 binary correctly starts up the JS > > interpreter on your ia64 install? > > Yeah, looks like 'js60' just returns 1. Huh? Shouldn't js60 simply start up the JS interpreter, giving a js> prompt, as for js38 in comment #18?
Yes. It appears to be broken for me as well. (Sorry, I see that my "Yeah" in comment #21 could have been interpreted as a statement that it worked correctly)
(In reply to Émeric Maschino from comment #18) > (In reply to Matt Turner from comment #16) > > ia64 stable > > How did you get it? sm60 simply fails to initialize JS, leading to bug > #701052 and bug #701054, thus blocking bug #685254. > > Even worse, while js38 correctly starts up the JS interpreter > > js> build() > built on Nov 21 2017 at 12:50:26 > js> quit() > > js60 gives absolutely nothing! In fact, I fear that the JS interpreter isn't > started at all. I doesn't seem to crash either, but I'm unable to rebuild > dev-lang/spidermonkey:60 with debugging symbols to double-check with GDB, as > =sys-auth/polkit-0.116-r1 installed on my system has a strong > dev-lang/spidermonkey:60[-debug] dependency. > > Can you please check that your js60 binary correctly starts up the JS > interpreter on your ia64 install? > > Thanks, > > Émeric with no emerge --info I am not sure what you want or expect to be done to resolve the issue. If you would please attach the emerge --info I am more then willing to look into the problem.
(In reply to Jory A. Pratt from comment #24) > > with no emerge --info I am not sure what you want or expect to be done to > resolve the issue. If you would please attach the emerge --info I am more > then willing to look into the problem. Well, I didn't wanted to pollute this BR as bugs are normally not reported in STABLEREQ BRs but in separate BRs. I initially only wanted to check with Matt (who flagged =dev-lang/spidermonkey-60.5.2_p0-r2 ia64 stable) if it was my install or a side-effect of another packages on my system that was triggering the sm60 failures that are blocking bug #701052 and bug #701054. It's now clear from comment #23 that =dev-lang/spidermonkey-60.5.2_p0-r2 doesn't work on ia64. I don't know if it was working when Matt marked it ia64 stable or if it never works and was incorrectly marked ia64 stable at the time. The latter can be easily overlooked, as =dev-lang/spidermonkey-60.5.2_p0-r2 emerges and passes tests successfully. Simply, sm60 binary brings "nothing": it doesn't seem to crash but the JS interpreter isn't started either. And a simple test program fails in JS_Init() as reported in https://bugs.gentoo.org/701054#c6. So, where to go from here now? Sure, I can post the output of emerge --info. But keeping in line with the usual stabilizing approach, it would probably be more appropriate (i) to reopen this BR and (ii) that I create a separate BR explaining the issue on ia64 and blocking this one. Would this be OK? Émeric
(In reply to Jory A. Pratt from comment #24) > > with no emerge --info I am not sure what you want or expect to be done to > resolve the issue. If you would please attach the emerge --info I am more > then willing to look into the problem. I've filed a separate BR to look into this issue (bug #703538). Please reopen this one as UNRESOLVED. Thanks!
