Debian Bug report logs - #1108748
mozjs140: SharedArrayBuffer feature unavailable on armel

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: submit@bugs.debian.org

Subject: mozjs128: SharedArrayBuffer feature unavailable on armel

Date: Thu, 29 Aug 2024 11:43:09 +0100

Source: mozjs128
Version: 128.1.0-3
Severity: important
Tags: ftbfs
User: debian-arm@lists.debian.org
Usertags: armel
X-Debbugs-CC: debian-arm@lists.debian.org

After fixing #1079077, mozjs128 still fails to build on armel, because
the lack of lockless atomic operations results in the SharedArrayBuffer
feature being disabled, and that makes several tests fail.

This feature seems to be used in the implementation of features that don't
obviously require it, for example:

> ## non262/RegExp/split-trace.js: rc = 3, run time = 0.011209
> 887016: Trace RegExp.prototype[@@split] behavior.
> /home/smcv/mozjs/js/src/tests/non262/RegExp/split-trace.js:99:42 TypeError: SharedArrayBuffer is disabled
> Stack:
>   @/home/smcv/mozjs/js/src/tests/non262/RegExp/split-trace.js:99:42
> TEST-UNEXPECTED-FAIL | non262/RegExp/split-trace.js | (args: "") [0.0 s]

where split-trace.js:99 is:

> var ret = RegExp.prototype[Symbol.split].call(myRegExp, target);

I don't know enough JavaScript to know whether this is likely to be
fixable or ignorable, or whether we will have to remove mozjs128 and
therefore gjs from armel (which would require workarounds similar to
what we did when we removed them from s390x during the buster cycle).

The main reason we need gjs is GNOME Shell, and I suspect nobody is
actually using GNOME Shell on armel: it seems unlikely to work well
with an older CPU emulating floating-point in software using integer
operations. Removing GNOME Shell from armel would be annoying, because
we would either have to ensure that task-gnome-desktop is still installable
(as we did for s390x in buster) or convince the release/d-i teams that it's
OK for it not to be, but is probably more achievable than adding features
to an architecture that mozjs upstream doesn't intend to support.

A secondary reason why we have gjs is that some leaf GNOME applications
(e.g. clapper, foliate, gnome-maps) are written in JavaScript, and those
are somewhat more likely to have real users on armel.

    smcv

Message #16 received at 1080000@bugs.debian.org (full text, mbox, reply):

From: Bastian Germann <bage@debian.org>

To: 1080000@bugs.debian.org

Subject: mozjs128: SharedArrayBuffer feature unavailable on armel

Date: Tue, 8 Apr 2025 16:02:55 +0200

Control: affects -1 src:cjs

This is used now on cjs as well. So maybe cinnamon/cjs have to be removed
from armel as it was done for gnome-core/gjs to let cjs migrate to trixie.

Message #23 received at 1080000@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: Bastian Germann <bage@debian.org>, 1080000@bugs.debian.org

Cc: cjs@packages.debian.org, cinnamon@packages.debian.org, cinnamon-desktop-environment@packages.debian.org

Subject: Re: Bug#1080000: mozjs128: SharedArrayBuffer feature unavailable on armel

Date: Tue, 8 Apr 2025 15:33:11 +0100

On Tue, 08 Apr 2025 at 16:02:55 +0200, Bastian Germann wrote:
>This is used now on cjs as well. So maybe cinnamon/cjs have to be removed
>from armel as it was done for gnome-core/gjs to let cjs migrate to trixie.

Yes, see also 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081039#43 which 
outlines how the Cinnamon team can resolve this.

    smcv

Message #28 received at 1080000@bugs.debian.org (full text, mbox, reply):

From: Jeremy Bícha <jeremy.bicha@canonical.com>

To: Bastian Germann <bage@debian.org>, 1080000@bugs.debian.org

Cc: cjs@packages.debian.org

Subject: Re: Bug#1080000: mozjs128: SharedArrayBuffer feature unavailable on armel

Date: Tue, 8 Apr 2025 10:34:36 -0400

On Tue, Apr 8, 2025 at 10:06 AM Bastian Germann <bage@debian.org> wrote:
> This is used now on cjs as well. So maybe cinnamon/cjs have to be removed
> from armel as it was done for gnome-core/gjs to let cjs migrate to trixie.

Yes, I left comments on https://bugs.debian.org/1081039 with
suggestions on how to finish the cjs mozjs128 transition.

Thank you,
Jeremy Bícha

Message #45 received at 1108748-done@bugs.debian.org (full text, mbox, reply):

From: Jeremy Bícha <jbicha@debian.org>

To: 1108748-done@bugs.debian.org

Subject: Re: mozjs140: SharedArrayBuffer feature unavailable on armel

Date: Mon, 3 Nov 2025 15:15:33 -0500

armel no longer exists in Unstable or Testing and mozjs140 wasn't in
any previous Debian release, so closing this bug as obsolete.

Thank you,
Jeremy Bícha

Send a report that this bug log contains spam.