-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
Cross Compilation for arm64 on x64 fails #42544
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Where did you get the source tarball from? I'm pretty sure simulator-arm64.cc isn't built by the official distribution. edit: I was wrong, it's scraped at configure time from deps/v8/BUILD.gn. |
I used link on https://nodejs.org/en/download/ i.e. https://nodejs.org/dist/v16.14.2/node-v16.14.2.tar.gz |
Actually, no, because of the size, I downloaded xz archive: https://nodejs.org/dist/v16.14.2/node-v16.14.2.tar.xz |
Can confirm that the same happens by checking out the v16.14.2 git tag |
Can you check if HEAD of the master branch cross-compiles okay? I think there's a good chance 6ac1ccc fixed this. |
What I can say right now is that compilation of git tag v17.8.0 works fine I can try building HEAD of master later today |
Yes, I used 16.10.0 previously and it works fine. I try to find which version is breaking. |
So, I tried to build various versions and it is broken from 16.11.0. I also tried to apply Ben's suggested patch 6ac1ccc back to 16.14.2 and it works. Thank you very much Ben. |
I don't have any problem with it if it doesn't break the build. |
Here is a working patch link |
Version
16.14.2
Platform
Linux (Fedora 34 64bit)
Subsystem
No response
What steps will reproduce the bug?
I cross compile Node.js 16.14.2 from sources for 64bit arm on 64bit Intel PC. I use the following options:
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
No response
What do you see instead?
It fails with following:
Additional information
No response
The text was updated successfully, but these errors were encountered: