SHA256 Checksum OK for electron/rust/crates/xxhash-rust-0.8.12.crate. SHA256 Checksum OK for electron/rust/crates/zerocopy-0.7.35.crate.*** Error code 1
SHA256 Checksum OK for electron/rust/crates/zerocopy-derive-0.7.35.crate. SHA256 Checksum OK for electron/yarn-4.12.0.tgz.
No SHA256 checksum recorded for electron/electron42-42.11.1-node-modules.tar.xz.
No suitable checksum found for electron/electron42-42.11.1-node-modules.tar.xz.
SHA256 Checksum OK for electron/electron-electron-v42.11.1_GH0.tar.gz. SHA256 Checksum OK for electron/nodejs-node-v24.19.0_GH0.tar.gz.
SHA256 Checksum OK for electron/nodejs-nan-675cefebca42410733da8a454c8d9391fcebfbc2_GH0.tar.gz.
SHA256 Checksum OK for electron/Squirrel-Squirrel.Mac-0e5d146ba13101a1302d59ea6e6e0b3cace4ae38_GH0.tar.gz.
SHA256 Checksum OK for electron/ReactiveCocoa-ReactiveObjC-74ab5baccc6f7202c8ac69a8d1e152c29dc1ea76_GH0.tar.gz.
SHA256 Checksum OK for electron/Mantle-Mantle-2a8e2123a3931038179ee06105c9e6ec336b12ea_GH0.tar.gz.
SHA256 Checksum OK for electron/EngFlow-reclient-configs-955335c30a752e9ef7bff375baab5e0819b6c00d_GH0.tar.gz.
SHA256 Checksum OK for electron/rollup-rollup-v4.22.4_GH0.tar.gz.
SHA256 Checksum OK for electron/evanw-esbuild-v0.28.1_GH0.tar.gz.
Stop.
make: stopped making "checksum" in /usr/ports/devel/electron42
However, that was the first step.
Now it fails with a several instances of the following error:
[ 0% 31/42842] python3 ../../third_party/node/node.pyI cherry-picked devel/esbuild from main and it seems to work
../../third_party/devtools-frontend/src/scripts/build/esbuild.js
gen/third_party/devtools-frontend/src/front_end/entrypoints/formatter_worker/FormatterActions.prebundle.js
gen/third_p
arty/devtools-frontend/src/front_end/entrypoints/formatter_worker/FormatterActions.js
--configSourcemaps --minify FAILED: [code=1]
gen/third_party/devtools-frontend/src/front_end/entrypoints/formatter_worker/FormatterActions.js
python3 ../../third_party/node/node.py
../../third_party/devtools-frontend/src/scripts/build/esbuild.js
gen/third_party/devtools-frontend/src/front_end/entrypoints/formatter_worker/FormatterActions.prebundle.js
gen/third_party/devtools-fr
ontend/src/front_end/entrypoints/formatter_worker/FormatterActions.js
--configSourcemaps --minify Traceback (most recent call last):
File
"/wrkdirs/usr/ports/devel/electron42/work/src/out/Release/../../third_party/node/node.py",
line 54, in <module> RunNode(sys.argv[1:]) File
"/wrkdirs/usr/ports/devel/electron42/work/src/out/Release/../../third_party/node/node.py",
line 49, in RunNode raise RuntimeError('Command \'%s\' failed\n%s'
% ( RuntimeError: Command
'/wrkdirs/usr/ports/devel/electron42/work/src/out/Release/../../third_party/node/freebsd/node-freebsd/bin/node
../../third_party/devtools-frontend/src/scripts/build/esbuild.js
gen/third_party/devtools-frontend/src/fr
ont_end/entrypoints/formatter_worker/FormatterActions.prebundle.js
gen/third_party/devtools-frontend/src/front_end/entrypoints/formatter_worker/FormatterActions.js
--configSourcemaps --minify' failed stderr: rLy [ERROR] Cannot start
service: Host version "0.28.1" does not match binary version
"0.28.0"
1 error
Failed to run esbuild: Error: The service was stopped: write EPIPE
at
/wrkdirs/usr/ports/devel/electron42/work/src/esbuild/npm/esbuild/lib/main.js:1230:34
at responseCallbacks.<computed>
(/wrkdirs/usr/ports/devel/electron42/work/src/esbuild/npm/esbuild/lib/main.js:884:9)
at afterClose
(/wrkdirs/usr/ports/devel/electron42/work/src/esbuild/npm/esbuild/lib/main.js:875:28)
at
/wrkdirs/usr/ports/devel/electron42/work/src/esbuild/npm/esbuild/lib/main.js:2276:18
at onwriteError (node:internal/streams/writable:603:3) at
process.processTicksAndRejections
(node:internal/process/task_queues:92:21)
If error includes `Host version "X" does not match binary version
"Y", you need to run `gclient sync`
exit=1
(though it will possibly take a couple of day to get to the finish
line).
I have made some changes to the port to always use the esbuild binary provided by the npm package registry to avoid such a discrepancy. It
has been committed to 2026Q3 branch at:
https://cgit.freebsd.org/ports/commit/?h=2026Q3&id=fa692c5de51140a5f4bff0b6e6ab81dbcc23ed8e
Please try again and let me know if it solves the problem.
Cheers,
Hiroki
I have made some changes to the port to always use the esbuild binary provided by the npm package registry to avoid such a discrepancy. It has been committed to 2026Q3 branch at:
https://cgit.freebsd.org/ports/commit/? h=2026Q3&id=fa692c5de51140a5f4bff0b6e6ab81dbcc23ed8e
Please try again and let me know if it solves the problem.
Please try again and let me know if it solves the problem.Right now, unfortunately I can't.
I managed to build it for all the OS versions I use and it would take
about 3 days to build it again, almost blocking my server during that time I'll keep this in mind and remove the esbuild upgrade I picked, when
I'll need to build it again for other reasons.
I have made some changes to the port to always use the esbuild binary provided by the npm package registry to avoid such a discrepancy. It has been committed to 2026Q3 branch at:Looks like it works.
https://cgit.freebsd.org/ports/commit/? h=2026Q3&id=fa692c5de51140a5f4bff0b6e6ab81dbcc23ed8e
Please try again and let me know if it solves the problem.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 74 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 122:26:10 |
| Calls: | 1,194 |
| Files: | 1,352 |
| Messages: | 290,355 |