Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1114180 > unrolled thread

Bug#1017962: mozjs102: Fails to build on armhf

Started byJeremy Bicha <jeremy.bicha@canonical.com>
First post2022-08-23 02:30 +0200
Last post2022-08-23 22:10 +0200
Articles 4 — 2 participants

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1017962: mozjs102: Fails to build on armhf Jeremy Bicha <jeremy.bicha@canonical.com> - 2022-08-23 02:30 +0200
    Bug#1017962: mozjs102: Fails to build on armhf Simon McVittie <smcv@debian.org> - 2022-08-23 11:20 +0200
      Bug#1017962: mozjs102: Fails to build on armhf Simon McVittie <smcv@debian.org> - 2022-08-23 11:40 +0200
        Bug#1017962: mozjs102: Fails to build on armhf Simon McVittie <smcv@debian.org> - 2022-08-23 22:10 +0200

#1114180 — Bug#1017962: mozjs102: Fails to build on armhf

FromJeremy Bicha <jeremy.bicha@canonical.com>
Date2022-08-23 02:30 +0200
SubjectBug#1017962: mozjs102: Fails to build on armhf
Message-ID<EXpXP-2oVT-5@gated-at.bofh.it>
Source: mozjs102
Version: 102.2.0-1
Severity: important
X-Debbugs-CC: debian-arm@lists.debian.org
Tags: ftbfs help

mozjs102 fails to build on armhf. This is a problem because it is
blocking us from being able to switch Debian's gjs to use mozjs102
instead of the obsolete mozjs91.

https://buildd.debian.org/status/logs.php?pkg=mozjs102&arch=armhf

Here's an excerpt from the build log:

In function ‘uint64_t js::jit::AtomicCmpXchg64SeqCst(uint64_t*,
uint64_t, uint64_t)’,
    inlined from ‘static T
js::jit::AtomicOperations::fetchAndSeqCst(T*, T) [with T = long long
int]’ at /<<PKGBUILDDIR>>/js/src/jit/shared/AtomicOperations-shared-jit.h:337:1,
    inlined from ‘static T
js::jit::AtomicOperations::fetchAndSeqCst(SharedMem<T*>, T) [with T =
long long int]’ at
/<<PKGBUILDDIR>>/js/src/jit/AtomicOperations.h:212:26,
    inlined from ‘virtual bool
cls_testAtomicOperationsI64::run(JS::HandleObject)’ at
/<<PKGBUILDDIR>>/js/src/jsapi-tests/testAtomicOperations.cpp:223:3:
/<<PKGBUILDDIR>>/debian/build/js/src/jit/AtomicOperationsGenerated.h:240:17:
error: ‘asm’ operand has impossible constraints
  240 |                 asm volatile (
      |                 ^~~


Thank you,
Jeremy Bicha

[toc] | [next] | [standalone]

#1114210

FromSimon McVittie <smcv@debian.org>
Date2022-08-23 11:20 +0200
Message-ID<EXyeK-2uBr-3@gated-at.bofh.it>
In reply to#1114180
On Mon, 22 Aug 2022 at 20:25:54 -0400, Jeremy Bicha wrote:
> mozjs102 fails to build on armhf
...
> In function ‘uint64_t js::jit::AtomicCmpXchg64SeqCst(uint64_t*,
> uint64_t, uint64_t)’,
>     inlined from ‘static T
> js::jit::AtomicOperations::fetchAndSeqCst(T*, T) [with T = long long
> int]’ at /<<PKGBUILDDIR>>/js/src/jit/shared/AtomicOperations-shared-jit.h:337:1,
>     inlined from ‘static T
> js::jit::AtomicOperations::fetchAndSeqCst(SharedMem<T*>, T) [with T =
> long long int]’ at
> /<<PKGBUILDDIR>>/js/src/jit/AtomicOperations.h:212:26,
>     inlined from ‘virtual bool
> cls_testAtomicOperationsI64::run(JS::HandleObject)’ at
> /<<PKGBUILDDIR>>/js/src/jsapi-tests/testAtomicOperations.cpp:223:3:
> /<<PKGBUILDDIR>>/debian/build/js/src/jit/AtomicOperationsGenerated.h:240:17:
> error: ‘asm’ operand has impossible constraints
>   240 |                 asm volatile (

I'm doing a build on amdahl to get the contents of the generated header,
but it's going to take a while to get there.

The firefox source package is basically the same codebase and it compiled
successfully on armhf, which might be a useful data point?

    smcv

[toc] | [prev] | [next] | [standalone]

#1114212

FromSimon McVittie <smcv@debian.org>
Date2022-08-23 11:40 +0200
Message-ID<EXyop-2uEJ-1@gated-at.bofh.it>
In reply to#1114210

[Multipart message — attachments visible in raw view] — view raw

On Tue, 23 Aug 2022 at 10:10:53 +0100, Simon McVittie wrote:
> On Mon, 22 Aug 2022 at 20:25:54 -0400, Jeremy Bicha wrote:
> > mozjs102 fails to build on armhf
> ...
> > In function ‘uint64_t js::jit::AtomicCmpXchg64SeqCst(uint64_t*,
> > uint64_t, uint64_t)’,
> >     inlined from ‘static T
> > js::jit::AtomicOperations::fetchAndSeqCst(T*, T) [with T = long long
> > int]’ at /<<PKGBUILDDIR>>/js/src/jit/shared/AtomicOperations-shared-jit.h:337:1,
> >     inlined from ‘static T
> > js::jit::AtomicOperations::fetchAndSeqCst(SharedMem<T*>, T) [with T =
> > long long int]’ at
> > /<<PKGBUILDDIR>>/js/src/jit/AtomicOperations.h:212:26,
> >     inlined from ‘virtual bool
> > cls_testAtomicOperationsI64::run(JS::HandleObject)’ at
> > /<<PKGBUILDDIR>>/js/src/jsapi-tests/testAtomicOperations.cpp:223:3:
> > /<<PKGBUILDDIR>>/debian/build/js/src/jit/AtomicOperationsGenerated.h:240:17:
> > error: ‘asm’ operand has impossible constraints
> >   240 |                 asm volatile (
> 
> I'm doing a build on amdahl to get the contents of the generated header,
> but it's going to take a while to get there.

Here's the generated file. The build is still going, so I don't know
whether the FTBFS will be reproducible.

    smcv

[toc] | [prev] | [next] | [standalone]

#1114279

FromSimon McVittie <smcv@debian.org>
Date2022-08-23 22:10 +0200
Message-ID<EXInL-2AQn-9@gated-at.bofh.it>
In reply to#1114212
Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1761665

On Tue, 23 Aug 2022 at 10:27:02 +0100, Simon McVittie wrote:
> Here's the generated file. The build is still going, so I don't know
> whether the FTBFS will be reproducible.

Looks like yes. I think this is the same issue as
https://bugzilla.mozilla.org/show_bug.cgi?id=1761665 upstream,
so I'm trying the workaround suggested there.

    smcv

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web