Node.js v12.18.1 on armv6, armv7 and armv8 about pkg-binaries HOT 10 CLOSED

from pkg-binaries.

Yeah I misunderstood that comment then 🤣. check #9

from pkg-binaries.

@robertsLando Thanks for the clarification and also for the binaries 👍

from pkg-binaries.

@n1ru4l You welcome :)

from pkg-binaries.

@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 fetched-v12.18.1-linux-armv7 we are unable to build those.

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

from pkg-binaries.

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

from pkg-binaries.

@robertsLando Yeah I actually figured that out already 😅 So that means it should actually work today if I would place fetched-v12.18.1-linux-armv6 as fetched-v12.18.1-linux-armv7 in the cache, is that correct?

from pkg-binaries.

@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

from pkg-binaries.

So that means it should actually work today if I would place fetched-v12.18.1-linux-armv6 as fetched-v12.18.1-linux-armv7 in the cache, is that correct

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)

from pkg-binaries.

closed by #9

from pkg-binaries.