Package: emscripten Version: 3.1.66~dfsg-2 Followup-For: Bug #1081967 X-Debbugs-Cc: noisyc...@tutanota.com, elb...@debian.org, j...@debian.org
Hi Julian and Paul, I agree with Paul that Julian pushing his changes to a branch may be helpful. Indeed, for the sake of unblocking mesa's transition to testing, which is blocked by llvm-19's, which is blocked by llvm-15 removal, which is blocked by (among others) emscripten, I did some exploratory work and may be able to provide some patches for emscripten once the bug in [1] is solved. >From what I can see, asides from upgrading llvm, emscripten's dependency on binaryen must be upgraded too: `tools/link.py` uses a `--no-stack-ir` option which was introduced in binaryen v119. Using the latter, once [1] is solved (to be clear: I didn't solve it), one needs to bump eslint's ecmaVersion to 13 as required by emscripten, and then it looks like the autopkgtest will pass. See e.g. [2], where I temporarily disabled the linking error to see what else needs to be done. Note that binaryen v119 is not currently in unstable, so a version bump must be requested to the maintainer. I built it locally just to test emscripten's autopkgtests, without caring about its packaging and just making sure that it builds. To build on arm64 (I am on arm64) it neededs a patch, see [3]. Best. P.S.: I know very little about both emscripten and binaryen, so these patches need to be reviewed. [1] https://github.com/emscripten-core/emscripten/discussions/22656 [2] https://salsa.debian.org/NoisyCoil/emscripten/-/commits/3.1.66-3 [3] https://salsa.debian.org/NoisyCoil/binaryen/-/commits/119-1
