Source: mozjs128 Version: 128.1.0-1 Severity: important Tags: ftbfs User: debian-...@lists.debian.org Usertags: armel X-Debbugs-CC: debian-...@lists.debian.org
mozjs128 fails to build on armel, apparently because of atomic operations. Assistance is requested because we want to switch gjs from mozjs115 to mozjs128 soon. I attempted a very simple -latomic fix but it failed. mozjs has a more complicated buildsystem so maybe I didn't set it in the right place. https://salsa.debian.org/gnome-team/mozjs/-/commit/d5a129b11 Build log excerpt ========== In file included from /<<PKGBUILDDIR>>/js/src/jsapi-tests/testGCHeapBarriers.cpp:19: /<<PKGBUILDDIR>>/js/src/jsapi-tests/tests.h: In member function ‘virtual void JSAPIRuntimeTest::maybeAppendException(JSAPITestString&)’: /<<PKGBUILDDIR>>/js/src/jsapi-tests/tests.h:336:29: note: ‘s’ declared here 336 | JS::Rooted<JSString*> s(cx, JS::ToString(cx, v)); | ^ /<<PKGBUILDDIR>>/js/src/jsapi-tests/tests.h:328:55: note: ‘this’ declared here 328 | void maybeAppendException(JSAPITestString& message) override { | ^~~~~~~~ /usr/bin/ld: ../../../js/src/build/libjs_static.a(Interpreter.o): in function `std::__atomic_base<unsigned long long>::store(unsigned long long, std::memory_order)': Full build log ====== https://buildd.debian.org/status/package.php?p=mozjs128 Thank you, Jeremy Bícha
