Hi, On Thu, Sep 19, 2024 at 09:09:05PM +0200, Paul Gevers wrote: > Hi, > > On 19-09-2024 18:49, Julian Gilbey wrote: > > Ah! That would work. But I've now found the source of the problem, > > and have a suggestion for how to fix it. Shall I commit directly to > > the emscripten salsa repo? > > emscripten is QA maintained, so if you feel like you can responsibly change > the package, please go ahead.
OK, thanks! Shall do (but not before the weekend or some time next week). > I'd like to note that I also believe that the current version of emscripten > also need stuff from llvm-toolchain-19 instead of 18. The autopkgtest > failure of node-inwasm shows that the current version of emscripten uses a > too new option --no-growable-memory Oh, yeesh :/ > 98s emcc: warning: LLVM version for clang executable "/usr/bin/clang-18" > appears incorrect (seeing "18.1", expected "20") [-Wversion-check] > 98s wasm-ld-18: error: unknown argument: --no-growable-memory > > Fixing the autopkgtest of emscripten to run in test instead of in tests and > rebuilding [1] with 18 replaced by 19 in d/control shows that's not enough: > """ > emcc: warning: LLVM version for clang executable "/usr/bin/clang-19" appears > incorrect (seeing "19.1", expected "20") [-Wversion-check] > error: undefined symbol: _emscripten_tempret_set (referenced by > $setTempRet0, referenced by setTempRet0, referenced by root reference (e.g. > compiled C/C++ code)) > warning: To disable errors for undefined symbols use > `-sERROR_ON_UNDEFINED_SYMBOLS=0` > warning: __emscripten_tempret_set may need to be added to EXPORTED_FUNCTIONS > if it arrives from a system library > Error: Aborting compilation due to previous errors > emcc: error: '/usr/bin/node /usr/share/emscripten/src/compiler.mjs > /tmp/tmpinds__jv.json' failed (returned 1) > """ Oh dear, looks like this won't be so straightforward. Hmmm. Best wishes, Julian
