[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Help needed for node-quickjs-emscripten





Le lun. 14 avr. 2025 à 10:45, Jérémy Lal <kapouer@melix.org> a écrit :


Le lun. 14 avr. 2025 à 10:25, Yadd <yadd@debian.org> a écrit :
Hi all,

I'm unable to fix build/test issue of node-quickjs-emscripten. We need
to fix this because it's a reverse dependency of the whole node stack
(via src:node-proxy-agents -> node-undici)

Even if we remove the test dependency of node-undici, there are a lot of
packages that depends on src:node-proxy-agents:

Reverse-Testsuite-Triggers
==========================
* node-corepack                 (for node-proxy-agent)
* node-undici                   (for node-proxy)
* node-undici                   (for node-proxy-agent)

Reverse-Build-Depends
=====================
* node-corepack                 (for node-proxy-agent)
* node-fetch                    (for node-data-uri-to-buffer)
* node-jsdom                    (for node-https-proxy-agent)
* node-jsdom                    (for node-http-proxy-agent)
* node-playwright               (for node-socks-proxy-agent)
* node-playwright               (for node-https-proxy-agent)
* node-pre-gyp                  (for node-https-proxy-agent)
* node-ws                       (for node-https-proxy-agent)

Reverse-Depends
===============
* node-fetch                    (for node-data-uri-to-buffer)
* node-gyp                      (for node-https-proxy-agent)
* node-jsdom                    (for node-https-proxy-agent)
* node-jsdom                    (for node-http-proxy-agent)
* node-pre-gyp                  (for node-https-proxy-agent)
* node-ws                       (for node-https-proxy-agent)
* npm                           (for node-agent-base)
* npm                           (for node-http-proxy-agent)
* npm                           (for node-https-proxy-agent)


Can someone else have a look ?

Here's what I found so far:
node-quickjs-emscripten 0.23 is not compatible with emscripten 3.1.69.
The latest version 0.31 is compatible with emscripten 3.1.65, which is close enough that
backporting the emcc build flags could make it work.

compared to

Observe that:
- The source directory layout has changed a lot between versions
- The variants that are actually compiled in the debian package are only a small subset
- emscripten build flags change a lot between versions, and have huge effects on the executability of the resulting wasm.

Found it :)


Reply to: