Bug#1091032: node-inwasm: FTBFS: wasm-ld-18: error: unknown argument: --no-growable-memory

[Jérémy Lal <kapouer@melix.org>]

Package: emscripten
Followup-For: Bug #1091032
Control: tags -1 ftbfs

Hi,

I've successfully built emscripten and node-inwasm, for a start.
For now I don't know if the tests are okay (many hours, need limit the amount of variations),
but it works with binaryen 122 and llvm-19.

Most troubles will come from binaryen 122 (which is failing some test and at least
fails on armel).

It would make sense to me that pkg-javascript-devel takes on the maintenance
of both of these packages (emscripten and binaryen), these being essential
to the wasm ecosystem.

Jérémy 

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages emscripten depends on:
ii  binaryen    122-2
ii  ccache      4.10.2-1+b2
ii  clang-19    1:19.1.7-1+b1
ii  lld-19      1:19.1.7-1+b1
ii  llvm-19     1:19.1.7-1+b1
ii  node-acorn  8.8.1+ds+~cs25.17.7-2
ii  nodejs      20.18.2+dfsg-4
ii  python3     3.13.1-2

Versions of packages emscripten recommends:
ii  libjs-d3       3.5.17-4
ii  python3-numpy  1:2.2.2+ds-2

Versions of packages emscripten suggests:
ii  adb               1:34.0.5-6
ii  automake          1:1.17-3
pn  closure-compiler  <none>
ii  cmake             3.31.5-2
pn  emscripten-doc    <none>
ii  make              4.4.1-1
ii  python3-ply       3.11-7
ii  scons             4.8.1+dfsg-1
pn  wabt              <none>

-- no debconf information