Repository navigation
Closed as not planned
Labels
armIssues and PRs related to the ARM architecture.Issues and PRs related to the ARM architecture.buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
Description
Version
16.14.2
Platform
Linux bx.ee 5.4.0-89-generic #100-Ubuntu SMP Fri Sep 24 14:50:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
./configure --cross-compiling --dest-cpu arm64 --dest-os linux && make -j8
How often does it reproduce? Is there a required condition?
Every time
What is the expected behavior?
If cross-compiling is supported, I would expect that supplying the --cross-compiling flag would avoid attempting to run cross-compiled executables like icupkg on the host architecture which wouldn't rationally be expected to succeed.
What do you see instead?
LD_LIBRARY_PATH=/home/jgowdy/projects/build-node-pac/node/out/Release/lib.host:/home/jgowdy/projects/build-node-pac/node/out/Release/lib.target:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; cd ../tools/icu; mkdir -p /home/jgowdy/projects/build-node-pac/node/out/Release/obj/gen; "/home/jgowdy/projects/build-node-pac/node/out/Release/icupkg" -tl ../../deps/icu-tmp/icudt70l.dat "/home/jgowdy/projects/build-node-pac/node/out/Release/obj/gen/icudt70l.dat"
/bin/sh: 1: /home/jgowdy/projects/build-node-pac/node/out/Release/icupkg: Exec format error
Additional information
I did see #11931 however this isn't related to Android, just being able to cross-compile arm64 Linux binaries on amd64.
Metadata
Metadata
Assignees
Labels
armIssues and PRs related to the ARM architecture.Issues and PRs related to the ARM architecture.buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
Activity
jgowdy commentedon Apr 7, 2022
bnoordhuis commentedon Apr 9, 2022
icupkg's build rules say it should be built for the host arch, not the target arch.
The rules are in tools/icu/icu-generic.gyp. Note how icpupkg itself declares
'toolsets': ['host']and its dependents list it asicupkg#host.My guess is this is related to your local toolchains, it's not picking up the right one. Run
make AR_host=.. CC_host=.. CXX_host=..to point it to the host toolchain andAR_target=..etc. for the target toolchain.github-actions commentedon Jun 25, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon Jul 26, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.