Your message dated Fri, 14 Feb 2025 13:05:46 +0000 with message-id <E1tivO6-001TBP-Aw@fasolo.debian.org> and subject line Bug#1091032: fixed in emscripten 3.1.69+dfsg-1 has caused the Debian Bug report #1091032, regarding node-inwasm: FTBFS: wasm-ld-18: error: unknown argument: --no-growable-memory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1091032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091032 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: node-inwasm: FTBFS: wasm-ld-18: error: unknown argument: --no-growable-memory
- From: Lucas Nussbaum <lucas@debian.org>
- Date: Sun, 22 Dec 2024 10:02:36 +0100
- Message-id: <Z2fVrGsCF1711VvO@grub.nussbaum.fr>
Source: node-inwasm Version: 0.0.13~git20230419+dfsg-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lucas@debian.org Usertags: ftbfs-20241222 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > tsc -p inwasm > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_auto_test --buildsystem=nodejs > /!\ ./package.json not found > ln -s ../debian/tests/test_modules/source-map-loader node_modules/source-map-loader > ln -s ../inwasm node_modules/inwasm > /bin/sh -ex debian/tests/pkg-js/test > + cd testproject > + BIN=node ../inwasm/lib/cli.js > + [ != ] > + tsc > + grep -v example_rust.wasm.js > + grep -v example_zig.wasm.js > + ls lib/example_clang_c.wasm.js lib/example_custom.wasm.js lib/example_emscripten_c.wasm.js lib/example_rust.wasm.js lib/example_wat.wasm.js lib/example_zig.wasm.js > + node ../inwasm/lib/cli.js lib/example_clang_c.wasm.js lib/example_custom.wasm.js lib/example_emscripten_c.wasm.js lib/example_wat.wasm.js > [inwasm config] used configration: > APP_ROOT: /<<PKGBUILDDIR>>/inwasm > PROJECT_ROOT: /<<PKGBUILDDIR>>/testproject > { > zig: { version: 'master', store: 'project' }, > emsdk: { version: 'latest', store: 'project' } > } > [inwasm compile] Building lib/example_clang_c.wasm.js:add > /usr/bin/clang --target=wasm32-unknown-unknown --no-standard-libraries -Wl,--export=add -Wl,--no-entry -Wl,--lto-O3 -O3 -Wl,--initial-memory=0 -Wl,--max-memory=0 -Wl,--import-memory -Wl,-z,stack-size=0 -flto -o add.wasm add.c > > [inwasm compile] Successfully built 'add' (183 Bytes). > > clang-c add: 65 > memory bytelength: 0 > [inwasm compile] Building lib/example_custom.wasm.js:custom > [inwasm compile] Successfully built 'custom' (41 Bytes). > > custom module: [Object: null prototype] { add: [Function: 0] } > custom module add 23 + 42: 65 > [inwasm compile] Building lib/example_emscripten_c.wasm.js:convert-simd > /usr/bin/emcc -O3 -DCHUNK_SIZE=32768 -s EXPORTED_FUNCTIONS=_chunk_addr,_target_addr,_convert -msimd128 -msse -msse2 -mssse3 -msse4.1 --no-entry convert-simd.c -o convert-simd.wasm > emcc: warning: LLVM version for clang executable "/usr/bin/clang-18" appears incorrect (seeing "18.1", expected "20") [-Wversion-check] > wasm-ld-18: error: unknown argument: --no-growable-memory > emcc: error: '/usr/bin/wasm-ld-18 -o convert-simd.wasm -L/usr/share/emscripten/cache/sysroot/lib/wasm32-emscripten /tmp/emscripten_temp_gv6fxsjy/convert-simd_0.o /usr/share/emscripten/cache/sysroot/lib/wasm32-emscripten/crt1_reactor.o -lGL-getprocaddr -lal -lhtml5 -lstandalonewasm-nocatch -lstubs -lnoexit -lc -ldlmalloc -lcompiler_rt -lc++-noexcept -lc++abi-noexcept -lsockets -mllvm -combiner-global-alias-analysis=false -mllvm -enable-emscripten-sjlj -mllvm -disable-lsr /tmp/tmp59j32b0qlibemscripten_js_symbols.so --strip-debug --export=chunk_addr --export=target_addr --export=convert --export=emscripten_stack_get_current --export=_emscripten_stack_restore --export-if-defined=__start_em_asm --export-if-defined=__stop_em_asm --export-if-defined=__start_em_lib_deps --export-if-defined=__stop_em_lib_deps --export-if-defined=__start_em_js --export-if-defined=__stop_em_js --export-table -z stack-size=65536 --no-growable-memory --initial-heap=16777216 --entry=_initialize --table-base=1 --global-base=1024' failed (returned 1) > > Error: ENOENT: no such file or directory, open 'convert-simd.wasm' > at Object.openSync (node:fs:573:18) > at Object.readFileSync (node:fs:452:35) > at Object.default_1 [as C] (/<<PKGBUILDDIR>>/inwasm/lib/runners/emscripten_c.js:71:15) > at compileWasm (/<<PKGBUILDDIR>>/inwasm/lib/cli.js:287:65) > at processFile (/<<PKGBUILDDIR>>/inwasm/lib/cli.js:386:32) > at main (/<<PKGBUILDDIR>>/inwasm/lib/cli.js:606:19) > at process.processTicksAndRejections (node:internal/process/task_queues:95:5) { > errno: -2, > code: 'ENOENT', > syscall: 'open', > path: 'convert-simd.wasm' > } > dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 > make: *** [debian/rules:8: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2024/12/22/node-inwasm_0.0.13~git20230419+dfsg-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20241222;users=lucas@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20241222&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
- To: 1091032-close@bugs.debian.org
- Subject: Bug#1091032: fixed in emscripten 3.1.69+dfsg-1
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Fri, 14 Feb 2025 13:05:46 +0000
- Message-id: <E1tivO6-001TBP-Aw@fasolo.debian.org>
- Reply-to: Jérémy Lal <kapouer@melix.org>
Source: emscripten Source-Version: 3.1.69+dfsg-1 Done: Jérémy Lal <kapouer@melix.org> We believe that the bug you reported is fixed in the latest version of emscripten, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1091032@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal <kapouer@melix.org> (supplier of updated emscripten package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Thu, 13 Feb 2025 23:54:55 +0100 Source: emscripten Architecture: source Version: 3.1.69+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers <pkg-javascript-devel@alioth-lists.debian.net> Changed-By: Jérémy Lal <kapouer@melix.org> Closes: 1081967 1091032 Changes: emscripten (3.1.69+dfsg-1) unstable; urgency=medium . * New upstream version 3.1.69 * Update source-map-footer * Install node modules * Use esbuild to test for es6 syntax errors * Depends binaryen >= 120 * Move to Javascript Maintainers . [ Julian Gilbey ] * Fix provided CMake file (closes: #1081967) * Simplify /usr/bin wrapper * Install new binaries in /usr/bin * Add dependency on ccache * Fix some lintian errors and warnings * Update d/copyright (though it's probably not completely correct), and absorb "License-Grant" sections into "License" sections * Increase LLVM dependencies to version 19 (to support --no-growable-memory option) (Closes: #1091032) * Switch to using standard sphinx-rtd-theme * Change d/watch to rename upstream version as +dfsg instead of ~dfsg in future Checksums-Sha1: 68d5cb6cda856709369070d111709f2612220359 3017 emscripten_3.1.69+dfsg-1.dsc b1aee2b20072f8f86977095e4b062dec9b4b51bf 5504 emscripten_3.1.69+dfsg.orig-Xtypes.tar.xz 3f2febb1eab53f75928912a93da1925c58502806 19363704 emscripten_3.1.69+dfsg.orig.tar.xz e9a66306e82f3d08d23729fdc07a295b5cc59536 83532 emscripten_3.1.69+dfsg-1.debian.tar.xz 97f2c922a9c57d89a965381fcf122e9b4c30627e 11771 emscripten_3.1.69+dfsg-1_source.buildinfo Checksums-Sha256: e624fe6b68032bcaa47a73e4f9aad3de3348b73ed1d2b288afc4e7b6fd10269c 3017 emscripten_3.1.69+dfsg-1.dsc 274d9ff5686f7e28fd00873fe04202f07fb8f5c950c978842f9e43c35d9baf03 5504 emscripten_3.1.69+dfsg.orig-Xtypes.tar.xz 394804c47d38ca3f1fa37b0b12beba60c2b03e6d7d3140a4e658b6dc6fee4481 19363704 emscripten_3.1.69+dfsg.orig.tar.xz d1d6e09c27b4cf715f238213c20b07a222a09ee3a9f6e3cf4af3bdbd385ab277 83532 emscripten_3.1.69+dfsg-1.debian.tar.xz 284f802d71e830a6763459d0e95e1f6cbdbd53c7d7ca292c1fa663f3628f6d48 11771 emscripten_3.1.69+dfsg-1_source.buildinfo Files: 53ca5d88c817e9b811215089d55c67af 3017 devel optional emscripten_3.1.69+dfsg-1.dsc 0bd105977cbfdf748cde9df40c63d408 5504 devel optional emscripten_3.1.69+dfsg.orig-Xtypes.tar.xz 50e8e18bb13e220109be79282df84eb6 19363704 devel optional emscripten_3.1.69+dfsg.orig.tar.xz 7876e0c9c2946b109c12dd7bc8426f93 83532 devel optional emscripten_3.1.69+dfsg-1.debian.tar.xz 62b8ec0802c6432bd3162b7ebf84f0ad 11771 devel optional emscripten_3.1.69+dfsg-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJGBAEBCAAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmeufhISHGthcG91ZXJA bWVsaXgub3JnAAoJEGYRwF7dOfN0bqsQAJQ2feP1L2RW7jPZXlEYI7MIZ6M2TCpa 52zQ6uFQF6DULV2TjDHCVRTHeE7dyviP0iam9a4NlkKRjC4k9kQRL1snky2KO9EY y8vwbbtmEDKUKfYLKUmr8fNYqzXOIRYEYzKjhxxGzc+1T/8YrkzakIihB9BfxtJq BdOBVeb7pYybITcJ4FTEKJp5L4SO0e6H8twbMeppSw+z9R5vROWfTU3xtKNiF/ZZ O0Y7Pw3EJGYyJMpi7RAUXZKIWhaRp85IZRcjHdkdT3H46cLxglgqjBxxWovyavK/ xAR/CYK4Kn6uuFxPz80eMqY7Lg0ZLCVUJ5DCrOyuY+m6IwOY57wXesdL1BhfVgLy 8BIBTFVX2//b97OMBQXtWJnrXCK6SGC0QdAMKDso1MNwW8g0NyE/wEOIFqva8YMY TBhPZdQFsJTwvhzcUdXPoMZnxzEmzhkbvHd6MtqEwwfc5Y2WReX0pC/hMN47oYyP iYf7dpfUTgcs3nrk/BEvOlgdQX11cKVWBmJC0y8eLWenAGsF9XR0vEUZ9nwQKy85 0HKl8C6EnWBTO9SBqkbivyX+AAh71ZChpgEyOJGBBIduo3qMXTasx71XppGxVvdv Rn0OvFaop8m+upZvDFItAElMR3iXxFOlEcwCcCj70R6ibft8IIaV9B+dkDVNSPH4 Brc/CYXCIAul =Eq25 -----END PGP SIGNATURE-----Attachment: pgpzRk3JE5Klh.pgp
Description: PGP signature
--- End Message ---