nodejs / nodejs/node

Cross-build x64 host -> arm target fails in V8 host arch guard (v8config.h)

Open
#61,794 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

build
Dominant language
JavaScript
Stars
122k
Forks
37.3k
Avg merge
4d 2h
Merged PRs (30d)
283

Description

Summary

Cross-building Node.js for --dest-cpu=arm (32-bit ARM / armhf) from an x64 Linux host fails in V8 host object compilation due to a host/target architecture guard in deps/v8/include/v8config.h.

Environment

  • Host: Ubuntu 24.04 x86_64
  • Target: Raspberry Pi 3, 32-bit Raspbian Buster (armhf)
  • Cross toolchain: arm-linux-gnueabihf-*

Repro

From x64 host:

./configure \
  --dest-os=linux \
  --dest-cpu=arm \
  --cross-compiling \
  --with-arm-float-abi=hard \
  --with-arm-fpu=neon \
  --without-node-snapshot
make -j1

Failure

Host V8 compilation fails with:

#error Target architecture arm is only supported on arm and ia32 host

Coming from deps/v8/include/v8config.h:

#if (V8_TARGET_ARCH_ARM && !(V8_HOST_ARCH_IA32 || V8_HOST_ARCH_ARM))
#error Target architecture arm is only supported on arm and ia32 host
#endif

In generated host makefiles (for example out/tools/v8_gypfiles/v8_libplatform.host.mk), host objects are compiled with -DV8_TARGET_ARCH_ARM, which triggers this guard on x64 hosts.

Notes

  • --without-node-snapshot does not avoid this, as host V8 objects are still built with ARM target macros.
  • A local workaround changing the guard to include x64 host allows compilation to proceed:
-#if (V8_TARGET_ARCH_ARM && !(V8_HOST_ARCH_IA32 || V8_HOST_ARCH_ARM))
+#if (V8_TARGET_ARCH_ARM && !(V8_HOST_ARCH_IA32 || V8_HOST_ARCH_ARM || V8_HOST_ARCH_X64))

Request

What is the intended/supported path for x64-host -> arm-target cross-builds in current Node/V8?

If this should be supported, could build generation be adjusted so host-side V8 tools/objects do not fail this guard (or guard logic updated in a supported way)?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the x64-to-arm build with the configure and make commands in the issue. Start with deps/v8/include/v8config.h and the generated out/tools/v8_gypfiles/v8_libplatform.host.mk, then trace why host objects receive the ARM target macro. Done means the supported cross-build path and the required guard or build-generation behavior are documented and verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, javascript, linux
Domain
build-system, compilers, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.