Skip to content

feat(js-runtime): support powerpc64 and powerpc64le - #3182

Open
pkubaj wants to merge 1 commit into
voidzero-dev:mainfrom
pkubaj:ppc64-fbsd-fix
Open

pkubaj wants to merge 1 commit into
voidzero-dev:mainfrom
pkubaj:ppc64-fbsd-fix

Conversation

@pkubaj

@pkubaj pkubaj commented Oct 21, 2026

Copy link
Copy Markdown

Arch::current() rejects every target other than x86_64 and aarch64
with a compile_error!, so vp cannot be built on PowerPC at all.

Add Arch::Ppc64 (big-endian) and Arch::Ppc64le (little-endian),
selected by target_endian because Rust uses the single target_arch
"powerpc64" for both. Their names follow Node.js's own process.arch
spelling, so on Linux ppc64le the managed runtime resolves the official
node-v<version>-linux-ppc64le.tar.gz.

Node.js publishes no big-endian Linux build. On ppc64 the download
stops before fetching any archive, with "Hash not found for
node-v-linux-ppc64.tar.gz in SHASUMS256.txt", while a
VP_NODE_DIST_MIRROR that carries such builds works unchanged.

`Arch::current()` rejects every target other than x86_64 and aarch64
with a `compile_error!`, so `vp` cannot be built on PowerPC at all.

Add `Arch::Ppc64` (big-endian) and `Arch::Ppc64le` (little-endian),
selected by `target_endian` because Rust uses the single target_arch
"powerpc64" for both. Their names follow Node.js's own `process.arch`
spelling, so on Linux ppc64le the managed runtime resolves the official
`node-v<version>-linux-ppc64le.tar.gz`.

Node.js publishes no big-endian Linux build. On ppc64 the download
stops before fetching any archive, with "Hash not found for
node-v<version>-linux-ppc64.tar.gz in SHASUMS256.txt", while a
VP_NODE_DIST_MIRROR that carries such builds works unchanged.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant