Bug 290980 - www/qt6-webengine: fails to duild when www/node24 is built without JIT
Summary: www/qt6-webengine: fails to duild when www/node24 is built without JIT
Status: In Progress
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-11-12 17:32 UTC by Dean E. Weimer
Modified: 2025-11-30 18:15 UTC (History)
5 users (show)

See Also:


Attachments
Compress full log of Poudreiere Build (255.47 KB, application/x-compressed)
2025-11-12 17:32 UTC, Dean E. Weimer
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dean E. Weimer 2025-11-12 17:32:34 UTC
Created attachment 265369 [details]
Compress full log of Poudreiere Build

www/qt6-webengine, build failing after update of devel/nspr from 4.38.1 to 4.38.2

[ 36% 8300/22849] /usr/local/bin/python3.11 ../../../../../qtwebengine-everywhere-src-6.9.3/src/3rdparty/chromium/build/gn_run_binary.py host/nasm -DPIC -felf64 -I../../../../../qtwebengine-everywhere-src-6.9.3/src/3rdparty/chromium/third_party/libvpx/source/config/ -I../../../../../qtwebengine-everywhere-src-6.9.3/src/3rdparty/chromium/third_party/libvpx/source/libvpx/ -I../../../../../qtwebengine-everywhere-src-6.9.3/src/3rdparty/chromium/third_party/libvpx/source/config/linux/x64/ -I./ -I../../../../../qtwebengine-everywhere-src-6.9.3/src/3rdparty/chromium/ -Igen/ -DCHROMIUM -MD obj/third_party/libvpx/libvpx_asm/sad4d_sse2.o.d -o obj/third_party/libvpx/libvpx_asm/sad4d_sse2.o ../../../../../qtwebengine-everywhere-src-6.9.3/src/3rdparty/chromium/third_party/libvpx/source/libvpx/vpx_dsp/x86/sad4d_sse2.asm
[ 36% 8300/22849] /usr/local/bin/python3.11 ../../../../../qtwebengine-everywhere-src-6.9.3/src/3rdparty/chromium/third_party/devtools-frontend/src/scripts/build/typescript/ts_library.py --tsconfig_output_location gen/third_party/devtools-frontend/src/front_end/models/trace/lantern/simulation/devtools_entrypoint-bundle-tsconfig-tsconfig.json --deps ./simulation-tsconfig.json --front_end_directory gen/third_party/devtools-frontend/src/front_end/models/trace/lantern/simulation --sources gen/third_party/devtools-frontend/src/front_end/models/trace/lantern/simulation/simulation.prebundle.ts
[ 36% 8300/22849] /usr/local/bin/python3.11 ../../../../../qtwebengine-everywhere-src-6.9.3/src/3rdparty/chromium/build/gn_run_binary.py host/nasm -DPIC -felf64 -I../../../../../qtwebengine-everywhere-src-6.9.3/src/3rdparty/chromium/third_party/libvpx/source/config/ -I../../../../../qtwebengine-everywhere-src-6.9.3/src/3rdparty/chromium/third_party/libvpx/source/libvpx/ -I../../../../../qtwebengine-everywhere-src-6.9.3/src/3rdparty/chromium/third_party/libvpx/source/config/linux/x64/ -I./ -I../../../../../qtwebengine-everywhere-src-6.9.3/src/3rdparty/chromium/ -Igen/ -DCHROMIUM -MD obj/third_party/libvpx/libvpx_asm/highbd_sad4d_sse2.o.d -o obj/third_party/libvpx/libvpx_asm/highbd_sad4d_sse2.o ../../../../../qtwebengine-everywhere-src-6.9.3/src/3rdparty/chromium/third_party/libvpx/source/libvpx/vpx_dsp/x86/highbd_sad4d_sse2.asm
ninja: build stopped: subcommand failed.
*** [src/core/Release/amd64/QtWebEngineCore.stamp] Error code 1

make[3]: stopped in /wrkdirs/usr/ports/www/qt6-webengine/work/.build
1 error

make[3]: stopped in /wrkdirs/usr/ports/www/qt6-webengine/work/.build
*** [src/core/CMakeFiles/QtWebEngineCore_Release_amd64.dir/all] Error code 2

make[2]: stopped in /wrkdirs/usr/ports/www/qt6-webengine/work/.build
1 error

make[2]: stopped in /wrkdirs/usr/ports/www/qt6-webengine/work/.build
*** [all] Error code 2

make[1]: stopped in /wrkdirs/usr/ports/www/qt6-webengine/work/.build
1 error

make[1]: stopped in /wrkdirs/usr/ports/www/qt6-webengine/work/.build
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop.
make: stopped in /usr/ports/www/qt6-webengine
=>> Cleaning up wrkdir
===>  Cleaning for qt6-webengine-6.9.3
build of www/qt6-webengine | qt6-webengine-6.9.3 ended at 2025-11-12T00:17:20-06:00
build time: 00:09:42
!!! build failure encountered !!!
Comment 1 Christoph Moench-Tegeder freebsd_committer freebsd_triage 2025-11-12 21:26:42 UTC
Extremely unlikely to be related to nspr:
- the change from nspr 4.38.1 to 4.38.2 was a fix in the test suite, not installed code
- qt6-webengine build fine here with nspr, both with my (default) options as well as with your (from the build log) options.

On the other hand, the actual error from your build log is
: /wrkdirs/usr/ports/www/qt6-webengine/work/qtwebengine-everywhere-src-6.9.3/src/3rdparty/chromium/third_party/node/node_modules/@rollup/wasm-node/dist/wasm-node/bindings_wasm.js:369
: const wasmModule = new WebAssembly.Module(bytes);
:                   ^
: ReferenceError: WebAssembly is not defined
:     at Object.<anonymous> (/wrkdirs/usr/ports/www/qt6-webengine/work/qtwebengine-everywhere-src-6.9.3/src/3rdparty/chromium/third_party/node/node_modules/@rollup/wasm-node/dist/wasm-node/bindings_wasm.js:369:20)
:     at Module._compile (node:internal/modules/cjs/loader:1760:14)
:     at Object..js (node:internal/modules/cjs/loader:1893:10)
:     at Module.load (node:internal/modules/cjs/loader:1480:32)
:     at Module._load (node:internal/modules/cjs/loader:1299:12)
:     at TracingChannel.traceSync (node:diagnostics_channel:328:14)
:     at wrapModuleLoad (node:internal/modules/cjs/loader:244:24)
:     at Module.require (node:internal/modules/cjs/loader:1503:12)
:     at require (node:internal/modules/helpers:152:16)
:     at Object.<anonymous> (/wrkdirs/usr/ports/www/qt6-webengine/work/qtwebengine-everywhere-src-6.9.3/src/3rdparty/chromium/third_party/node/node_modules/@rollup/wasm-node/dist/native.js:6:5)
: Node.js v24.11.0

The only bell WebAssembly rings is https://cgit.freebsd.org/ports/commit/?id=1a1ef8585f5aa1151486a2f8f13d50c6294b1deb - did you touch the WASM option there or did that change cause anything to your build? Also, as this is coming from nodejs and nodejs default version changed recently https://cgit.freebsd.org/ports/commit/?id=7aab179e1e183bd57b9a7b1f35ea906090de48f2 - anything special to your node package?
Comment 2 Dean E. Weimer 2025-11-13 12:38:28 UTC
When checking back through previous build, that was successful used node22, the build that failed was appeared based on logs to be triggered because of the nspr update. But it alos showed that it used node24 instead of node22. I had node22 JIT enabled, but it was not on node24. I enabled JIT option on node24 and it built successfully.
Comment 3 Max Brazhnikov freebsd_committer freebsd_triage 2025-11-14 19:22:52 UTC
Is this build combination supported by the upstream? If not, there is nothing we can do.