-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support Node.JS v12 #8
Comments
I encountered the same issue and from my understanding now, its becuase bytecode_builtins_list_generator is not compiled for the host system |
There you go:
|
I am facing the same issue while cross-compiling nodejs version 13.1.0. Above changes are already there in configure.py, it is still not working though, bytecode_builtins_list_generator is getting compiled for the target machine, can someone please help here. |
Its probably due to this change in v13.0.1: nodejs/node#30021 |
Thanks for your prompt response. I tried compiling using --with-snapshots flag, still stuck with same issue (bytecode_builtins_list_generator is getting built for target machine). Could you please suggest something here? |
If you want to compile node 13 I think it would be easier to just revert this change: nodejs/node@2623ef0 and compile --without-snapshot (as long they did not any further conflicting changes). If you want to make snapshots work with cross-compiling you might want to take a closer look how termux did this, or maybe just use their binaries. I have not done this, I am still on node v12 for my android project. I would be interested in a solution once LTS switches to 14. |
Thanks a lot for all your help and suggestions. I am able to compile nodejs 13.0 using the steps mentioned in link - https://chrislea.com/2018/08/20/cross-compiling-node-js-for-arm-on-ubuntu/ |
Can you please share the version 13 compiles? arm and arm64? Thank you greatly! |
Want it too 😀 |
It worked when I was trying to build node.js v6.5.0 but failed with node.js v12.40.0
The part of the output is following:
The text was updated successfully, but these errors were encountered: