Open Marv-CZ opened 2 years ago
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 6ac1cccf9fd5 fixed this.
What I can say right now is that compilation of git tag v17.8.0 works fine Same for v16.10.0
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.
@targos is 6ac1ccc eligible for cherry-picking to the release branches? Looks low risk to me.
I don't have any problem with it if it doesn't break the build.
@Hypfer @Marv-CZ you want to take a stab at back-porting it? Details are here.
edit: deleted an OoO auto-reply from @Tronzo
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