riscv64 builds

[drom]

What happened with riscv64 builds?
The last release I see v21.7.2
Do we have issues building v22?

[mhdawson]

@sxa not sure if you are still tracking risv builds?

[sxa]

Looks like the last one that was attempted and produced logs was 202405021441-v22.1.0/riscv64.log
Based on the most recent v22 logs from the unofficial builds process this may be related to #135

Note: I won't be able to take a look in any more detail myself until next week but thank you for raising this

[sxa]

OK ignoring the fact it didn't kick off properly the build will fail because it's currently configured to use GCC 9 which doesn't support C++20 which the Node 22 build requires.
I'm doing a (native) test build on a machine I have running Armbian 24.5 with GCC13.2. I'm reasonably certain I've done this before but it will be good to verify with that exact node version. Once that's complete we can look at what might be required to get it going again.

[sxa]

I'm currently getting a problem with the native build test - an undefined symbol v8::internal::trap_handler::RegisterDefaultTrapHandler

[richardlau]

I'm currently getting a problem with the native build test - an undefined symbol v8::internal::trap_handler::RegisterDefaultTrapHandler

I think that might be nodejs/node#53115

[sxa]

I'm currently getting a problem with the native build test - an undefined symbol v8::internal::trap_handler::RegisterDefaultTrapHandler

I think that might be nodejs/node#53115

Looks like it - cherry picked 1d345299e5 from the branch on top of v22.5.1 and that allowed the build to complete.

[gounthar]

What would it take to compile natively 20.19.0 for risc-v?

[prabhu]

Sorry to hijack this thread. What's a good release branch (>20) that compiles cleanly with riscv64 qemu? Currently testing the waters but have a banana-pi BPI-F3 on route.

With gcc-13, getting the below error for 24.0.1

CXX(target) /home/appthreat.linux/node-24.0.1/out/Release/obj.target/v8_compiler/deps/v8/src/maglev/maglev-phi-representation-selector.o
In file included from ../deps/v8/src/codegen/macro-assembler.h:82,
                 from ../deps/v8/src/maglev/maglev-ir.cc:18:
../deps/v8/src/codegen/riscv/macro-assembler-riscv.h:409:13: error: explicit specialization in non-namespace scope ‘class v8::internal::MacroAssembler’
  409 |   template <>
      |             ^
../deps/v8/src/codegen/riscv/macro-assembler-riscv.h:557:13: error: explicit specialization in non-namespace scope ‘class v8::internal::MacroAssembler’
  557 |   template <>
      |             ^
make[2]: *** [tools/v8_gypfiles/v8_compiler.target.mk:377: /home/appthreat.linux/node-24.0.1/out/Release/obj.target/v8_compiler/deps/v8/src/maglev/maglev-ir.o] Error 1
make[2]: *** Waiting for unfinished jobs....
rm 89cb3b372d9992589092b025bf8a96639b954af6.intermediate 5fe75ae9f9be9351149465cf000faab2618094df.intermediate e26732a2c1a92d713b419648ea02285e0fd245e8.intermediate
make[1]: *** [Makefile:135: node] Error 2
make: *** [Makefile:1305: node-v24.0.1-linux-riscv64.tar] Error 2

uname -ar
Linux lima-dosai-riscv64-1 6.8.0-55-generic #57.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 21 14:05:51 UTC 2025 riscv64 riscv64 riscv64 GNU/Linux

[kxxt]

Hi, how are the unofficial builds for riscv64 going?

VSCodium is currently depending on the unofficial builds for riscv64 to build the REH client(which people will use when using open-remote-ssh plugin of VSCodium to do remote development on riscv64)
https://github.com/VSCodium/vscodium/blob/0fdce0c326ccceaab075ffac12336abb4f84407b/build/linux/package_reh.sh#L62

Is there anything I can do to improve the situation?

[hayzamjs]

RISCv64 musl builds will also be awesome

[alitariq4589]

Hello everyone, I can provide free RISC-V Runners for builds. I have a CI setup for RISC-V NodeJS releases here, which checks for the latest tag in the NodeJS official upstream repository and builds it on RISC-V (Milk-V Pioneer Box) and then releases it.

If this project needs a RISC-V runner, it can be registered at this URL.

[sxa]

Thanks for the offer @alitariq4589!

The next step for us here is probably to look at getting the unofficial builds (cross-compiled) scheduled again now that #175 is in, and then we can look at what we might be able to do with native building and testing within the CI going forward.

I guess the question releasing to the PR above is whether having them only using on systems with libc 2.39 would be a problem for people in this discussion thread. I know I personally have RISC-V systems which that won't work on ...

[EDIT: Looks like I'm getting a compiler error on Node 24 and head with the updated compiler, so we may not be quite ready to get those unofficial builds switched on yet, although Node 22 builds ok so we could probably switch that one on. Noting that I have successfully built node 24 natively on a RISC-V machine]

[gounthar]

I have a RISC-V GitHub runner with libc41 if that can help. 🤷

[gounthar]

I've created a release if you're interested: https://github.com/gounthar/unofficial-builds/releases/tag/v24.11.0 .