René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Promote RISC-V to an official architecture","articleBody":"### What is the problem this feature will solve?\n\nAllow to get and install the node binaries from the main download pages, not from the unofficial section.\r\n\r\nIndirectly this will allow to install `node` via `nvm` (the node version manager), which does not support unofficial builds (https://github.com/nvm-sh/nvm/issues/3171#issuecomment-1688378889)\r\n\n\n### What is the feature you are proposing to solve the problem?\n\nPromote the RISC-V architecture to a prime citizen.\r\n\r\n@sxa mentioned in https://github.com/nodejs/node/issues/49278#issuecomment-1688437271 that this should be possible, assuming someone is willing to help.\r\n\r\nHis main concern was the the lack of asm support in openssl, currently requiring `--openssl-no-asm` to pass the build. \r\n\r\nI took a look at the openssl source files and I noticed that RISC-V asm support was added in 3.1. \r\n\r\nIn [openssl/VERSION.dat](https://github.com/nodejs/node/blob/main/deps/openssl/openssl/VERSION.dat) I see that the current version in use is 3.0.10.\r\n\r\nWould it be possible to upgrade the node dependencies to 3.1.2? (Unfortunately I'm not familiar with your build system to do this myself).\r\n\r\nOnce this is done, we can further test if the RISC-V build passes without `--openssl-no-asm`.\r\n\r\n\r\n\n\n### What alternatives have you considered?\n\n_No response_","author":{"url":"https://github.com/ilg-ul","@type":"Person","name":"ilg-ul"},"datePublished":"2023-08-26T10:54:34.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":10},"url":"https://github.com/49332/node/issues/49332"}