It's looking as though mozjs128, and therefore the next gjs release,
will not support armel due to its lack of atomic instructions causing
relatively basic features to be disabled.
elfutils,
fuse3:native,
gir1.2-gio-2.0-dev,
- gjs:native [!alpha !hppa !ia64 !m68k !sh4 !sparc64 !x32],
+ gjs:native [!alpha !armel !hppa !ia64 !m68k !sh4 !sparc64 !x32],
gnupg <!nocheck>,
gobject-introspection,
gobject-introspection (>= 1.78.1-7~) <cross>,
cpio,
fuse3,
gir1.2-ostree-1.0,
- gjs [!alpha !hppa !ia64 !m68k !sh4 !sparc64 !x32],
+ gjs [!alpha !armel !hppa !ia64 !m68k !sh4 !sparc64 !x32],
gnupg,
ostree,
python3,
# other architectures mentioned here.
# The test that runs this script is automatically skipped if gjs isn't
# present.
-[alpha hppa ia64 m68k sh4 sparc64 x32]: missing-dep-for-interpreter gjs => gjs (usr/libexec/installed-tests/libostree/corrupt-repo-ref.js)
+[alpha armel hppa ia64 m68k sh4 sparc64 x32]: missing-dep-for-interpreter gjs => gjs (usr/libexec/installed-tests/libostree/corrupt-repo-ref.js)
--without-smack \
$(NULL)
-ifneq ($(filter alpha hppa ia64 m68k sh4 sparc64 x32,$(DEB_HOST_ARCH)),)
+ifneq ($(filter alpha armel hppa ia64 m68k sh4 sparc64 x32,$(DEB_HOST_ARCH)),)
configure_options += ac_cv_path_GJS=
endif