Riscv64 native

[fede2cr]

riscv64 hardware is getting larger (64-core and 192-core hardware are available), so this is a recipe to build in riscv64 hardware without the use of cross compiler or distro-external toolchains.

Tested with:
bin/local_build.sh -r riscv64-native -v v20.18.0

[rvagg]

Nice, but it probably doesn't belong here because these are all built in a single x64 Linux machine. So this won't run and produce anything.

[rvagg]

In theory both DESTCPU and ARCH should be detected automatically, so they may not be needed at all in the musl recipe; see https://github.com/nodejs/node/blob/main/Makefile#L934-L935 and then that might give you what you want - which I assume is an easy easy way of building Node.js in a container for your platform bundled like it's supposed to be? Because if we can't compile it on an x64 Linux machine then we can't publish it at unofficial-builds.nodejs.org (currently anyway), this just becomes an exercise in adding code that's not used by this particular project.

Try removing those two options and if you can tell me whether it builds successfully for your in riscv64 and x64 if you have access to both, then that would be very useful.

[wojiushixiaobai]

@rvagg
You are right, this will work, but we need to do some additional configuration to get it to work on riscv64 and loong64.

#!/usr/bin/env bash

set -e
set -x

release_urlbase="$1"
disttype="$2"
customtag="$3"
datestring="$4"
commit="$5"
fullversion="$6"
source_url="$7"
source_urlbase="$8"
config_flags=""
make_flags=""

alpineArch="$(apk --print-arch)"
case "${alpineArch##*-}" in
  riscv64)
    config_flags+="--openssl-no-asm"
    ;;
  loongarch64)
    make_flags+=" DESTCPU=loong64 ARCH=loong64"
    config_flags+="--openssl-no-asm"
    ;;
esac

cd /home/node

tar -xf node.tar.xz
cd "node-${fullversion}"

export CC="ccache gcc"
export CXX="ccache g++"

make_flags+=" \
  VARIATION=musl \
  DISTTYPE=$disttype \
  CUSTOMTAG=$customtag \
  DATESTRING=$datestring \
  COMMIT=$commit \
  RELEASE_URLBASE=$release_urlbase \
  CONFIG_FLAGS=$config_flags"

make -j$(getconf _NPROCESSORS_ONLN) binary V= $make_flags

mv node-*.tar.?z /out/

[rvagg]

OK, I don't think I mind, if it works. Is loong64 supported by Alpine already?

[wojiushixiaobai]

OK, I don't think I mind, if it works. Is loong64 supported by Alpine already?

Yes，
alpine linux 3.21.0 already supports loongarch64, but the alpine:3.21 container image is not ready yet.

• Alpine-3.21.0-released
• add loongarch64

[jameschensmith]

@wojiushixiaobai, alpine:3.21 is out now, by the way. I got here from #104, and if this PR unblocks that, I'd love to see if I could help out in any way. Trying to get a full understanding of the messages in this PR and the current files changed. Am I right in understanding there may be a plan to just use the musl recipe to build all the archs?

[wojiushixiaobai]

@jameschensmith
Currently GitHub Actions already provides aarch64 build support, we can easily verify this.
I will submit a PR later to see if the maintainers has any other comments.