Request for Loong64 Binaries in v24.4.1 and Future Releases

[Javonne-liu]

thank you so much for maintaining this repository—it’s an invaluable resource.
I noticed that the latest release, v24.4.1 (https://unofficial-builds.nodejs.org/download/release/v24.4.1/), currently includes Linux x64-musl binaries but no builds for the loong64 (LoongArch64) architecture.
Would it be possible to add loong64 builds for v24.4.1 and ensure they’re included in future releases?
Best regards,

[rvagg]

Looks like x64-glibc-217 is getting in the way: https://unofficial-builds.nodejs.org/logs/202507160208-v24.4.1/
It works through the recipes sequentially and when one breaks the ones after it break too. We'll need to block out x64-glibc-217 and try again: #177

Aaaand after trying that, loong has the same problem: https://unofficial-builds.nodejs.org/logs/202507290214-v24.4.1/loong64.log

[rvagg]

#174 probably gets us some of the way but doesn't touch loong64

[rvagg]

Disabling until someone can show up and fix this: #178 sorry

[Javonne-liu]

Disabling until someone can show up and fix this: #178 sorry禁用，直到有人出现并修复此问题： #178 抱歉

in PR #172 which uses Ubuntu 24.04 and Python 3.10, should address the loong64 build issues.

I noticed that the current build logs for v24.4.1 are still using the older environment. Would it be possible to update the build environment to align with the changes in PR #172 (Ubuntu 24.04 + Python 3.10) for the loong64 builds? This might help in generating the loong64 binaries successfully for v24.4.1 and future releases.

Appreciate your help on this!

cc: @Xiao-Tao @shipujin

[Xiao-Tao]

What do I need to do to update the loong64 build environment? @rvagg
I'd love to see a re-build of the loong64 architecture.

[shipujin]

Disabling until someone can show up and fix this: #178 sorry禁用，直到有人出现并修复此问题： #178 抱歉

in PR #172 which uses Ubuntu 24.04 and Python 3.10, should address the loong64 build issues.

I noticed that the current build logs for v24.4.1 are still using the older environment. Would it be possible to update the build environment to align with the changes in PR #172 (Ubuntu 24.04 + Python 3.10) for the loong64 builds? This might help in generating the loong64 binaries successfully for v24.4.1 and future releases.  Appreciate your help on this!

cc: @Xiao-Tao @shipujin

https://unofficial-builds.nodejs.org/logs/202507290214-v24.4.1/loong64.log

loong64.log compilation error requires the python version in the current docker_rootfs to be greater than 3.8

build: drop support for python 3.8

[Xiao-Tao]

The build environment for loong64 has been updated to use Ubuntu 24.04 and Python 3.10. https://github.com/nodejs/unofficial-builds/blob/main/recipes/loong64/Dockerfile#L18

loong64.log compilation error requires the python version in the current docker_rootfs to be greater than 3.8

build: drop support for python 3.8

How can I synchronize this environment with the Docker container used for building?

[vitaliylag]

Old comment (the reason of the error was different)

There is a bug in Makefile which leads to Python version incompatibility.

As workaround I use this approach to choose Python version (in my pull request #174):

isNodeVersionGE() {
	printf "$1\n$fullversion" | sort -VC
}

setPython() {
	if isNodeVersionGE 'v22.3';  then export PYTHON='python3.13';  return;  fi  # Python 3.13: Node.js v22.3  ~ latest (v24.3)
	if isNodeVersionGE 'v14.14'; then export PYTHON='python3.9';   return;  fi  # Python 3.9:  Node.js v14.14 ~ latest (v24.3)
	if isNodeVersionGE 'v4.0';   then export PYTHON='python2.7';   return;  fi  # Python 2.7:  Node.js v4.0   ~ v15.14 (latest)
}

So I set PYTHON variable.

Explanation:

When you run "./configure" and then "make", "configure" finds appropriate python version automatically.

But when you run "make" it runs "$PYTHON ./configure" and "configure" is executed as python script. In this case "configure" does not perform search of appropriate python version and just uses current version. $PYTHON is set to python3 by default.

So you need to:

• Set $PYTHON to needed version
• Or run rm -f /usr/local/bin/python3 && ln -s "$(which python3.10)" /usr/local/bin/python3
• Or run "./configure" and then "make"
• Or fix it in "Makefile" and make pull request to https://github.com/nodejs/node

[vitaliylag]

Fix:
#181