-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Node.js v12.18.1 on armv6, armv7 and armv8 #7
Comments
They are there. Remember that armv6 can also be used in armv7 and armv8 is equal to arm64
…---
Daniel
On 7 Jul 2020, at 13:25, Laurin Quast ***@***.***> wrote:
Would it be possible to also build binaries for Node.js v12.18.1 for armv6, armv7, and armv8?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@robertsLando Thanks for the clarification and also for the binaries 👍 |
@n1ru4l You welcome :) |
@robertsLando So we are finally trying to upgrade to Node12 now and we run into a few complications. We are using docker buildx for creating armv7 binaries (since armv6 is not available as a docker image) and not supported by debian and dropped by Node.js). This means without a Could you please consider providing binaries for armv7? Edit: It seems building armv7 is currently broken for pkg (at least in docker buildx), as the architecture cannot be resolved reliably. This PR should fix that: https://github.com/vercel/pkg-fetch/pull/101/files |
Your edit is the answer to your question :) Once that is sorted I will update the build script, actually if you chech how I build now you will see I select armv6 even for armv7 build on purpose to fix that |
@robertsLando Yeah I actually figured that out already 😅 So that means it should actually work today if I would place |
@n1ru4l Unfortunally I rarely see a PR to be merged or at least considered with both pkg or pgk-fetch, if you don't see any response I could consider to use your branch to build pkg |
That is what I'm doing in last year and I didn't have any problem. Using armv6 binaries in armv7 seems safe, just rename it and it works :) As I said in my first comment here: #7 (comment) |
Yeah I misunderstood that comment then 🤣. check #9 |
closed by #9 |
Would it be possible to also build binaries for Node.js v12.18.1 for armv6, armv7, and armv8?
The text was updated successfully, but these errors were encountered: