Repository navigation
Add FreeBSD aarch64 to the list of supported platforms #67217
Description
What is the problem this feature will solve?
Do not limit FreeBSD support by amd64 only. This would allow package maintainers to ship aarch64 binding
What is the feature you are proposing to solve the problem?
I am proposing to include aarch64 FreeBSD to the list of the supported platforms, same as x64 now. The aarch64 port is working well; I am not aware of any arch-specific issues.
What alternatives have you considered?
No response
Activity
MikeMcC399 commentedon Nov 3, 2026
Currently, FreeBSD / x64 is listed as "Experimental" support type in the Platform list:
MikeMcC399 commentedon Nov 3, 2026
Do you have any comment on the open issue #40467 for FreeBSD on x64?
samm-git commentedon Nov 3, 2026
FreeBSD 13 has been EoL for a long time. I am a FreeBSD ports committer (samm@freebsd.org). The usual way to install Node.js is by using ports/pkg. This automates the build and includes all patches and verified configuration keys. Currently relevant ports are https://www.freshports.org/www/node26/ and https://www.freshports.org/www/node24/ and node22. I am using both on amd64 and aarch64.
samm-git commentedon Nov 3, 2026
P.S. Also, if there is anything I can do to move from "experimental" to Tier 2, please let me know.
seanm commentedon Nov 3, 2026
#40467 is using ports too. Only difference is that I'm building the ports myself, instead of using the ones built by someone else. The bug applies to anyone, even the people building the official FreeBSD binaries use the same mechanism (poudriere) and presumably have had to disable w^x too.
samm-git commentedon Nov 3, 2026
@seanm ok, the description was not clear enough, and yes, I never tried with w^x enabled. I can try to do it to see how it goes. On the other hand, this is custom hardening and shouldn't block Tier 2 status.