Closed nschonni closed 2 months ago
If anyone wants to tackle armv6l, the path I'd take is to just produce a new https://github.com/rvagg/rpi-newer-crosstools with a the minimum compiler and libc needed to support node. It looks like there's newer crosstools-ng that support up to gcc 13 so it shouldn't be too hard. I think I explain the process in that repo about taking an existing config and running a newer crosstools-ng and picking new versions.
I think what we should do if/when we get a newer rpi-newer-crosstools to use is make a new recipe that takes over for Node 22+, so we keep the old one stable. The catch might be the naming, I think we name the binaries according to the recipe name so maybe we should fix that so two recipes can share the same name as long as both aren't running for a particular version.
Since Node 16 isn't supported anyway, I swapped the check to match #142
v22 errors can be seen in https://unofficial-builds.nodejs.org/logs/202404242143-v22.0.0/armv6l.log in case someone wants to try and fix it later