Skip to content

ci: Disable armv6l on Node 22+#143

Merged
rvagg merged 1 commit intonodejs:mainfrom
nschonni:patch-1
Apr 29, 2024
Merged

ci: Disable armv6l on Node 22+#143
rvagg merged 1 commit intonodejs:mainfrom
nschonni:patch-1

Conversation

@nschonni
Copy link
Copy Markdown
Member

@nschonni nschonni commented Apr 29, 2024

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

@nschonni nschonni mentioned this pull request Apr 29, 2024
@rvagg rvagg merged commit f298882 into nodejs:main Apr 29, 2024
@rvagg
Copy link
Copy Markdown
Member

rvagg commented Apr 29, 2024

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.

@nschonni nschonni deleted the patch-1 branch April 30, 2024 06:08
@friebi
Copy link
Copy Markdown
Contributor

friebi commented Apr 13, 2025

@rvagg I was able to successfully compile and run 22.14.0 for my Raspberry Pi Zero. Here I described the few changes I made: #162 (comment).
Maybe you want to take a look and reactivate it 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants