search

nodejs / unofficial-builds

Unofficial binaries for Node.js
https://unofficial-builds.nodejs.org
242 stars 50 forks source link

riscv64 builds #150

Open drom opened 1 month ago

drom commented 1 month ago

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

mhdawson commented 1 month ago

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

sxa commented 1 month ago

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 https://github.com/nodejs/unofficial-builds/issues/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 commented 1 month ago

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 commented 1 month ago

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

richardlau commented 1 month ago

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

I think that might be https://github.com/nodejs/node/issues/53115

sxa commented 1 month ago

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

I think that might be https://github.com/nodejs/node/issues/53115

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