Can I run Node.js 20 on Slackware 14.2

I develop an app that needs to run on both Slackware 14.2 and 15.0
In the CI pipeline by Azure DevOps there are two Slackware containers running the build.
(App is distributed as source, but the CI verifies that it compiles for both)

The Slackware 14.2 build currently shows this warning about Node.js

##[warning]The container operating system doesn't support Node20. Using Node16 instead. Please upgrade the operating system of the container to remain compatible with future updates of tasks: https://github.com/nodesource/distributions

This is not a problem now, but it may be in the future.

I looked into upgrading Node.js, but failed:
- I changed the version in the 14.2 Slackbuild, but the the folder structure is different now.
- I tried the 15.0 Slackbuild on 14.0, but it requires a newer version of gcc (> 10)
- The binary distribution doesn't work, because of incompatible glibc:
root@64ecb24028c2 (32bit):/nodejs/node-v20.11.0-linux-x64/bin# ./node
./node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by ./node)
./node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by ./node)
./node: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by ./node)
- I tried the 15.0 Slackbuild with a custom toolchain (with old glibc), but ran into issues with openssl. The one on SL14.2 might be too old.

Is there any chance to pull this off? Or is it just not feasible?

####################################################################
# NOTICE OF INPENDING EOL (END OF LIFE) FOR OLD SLACKWARE VERSIONS #
#                                                                  #
# Effective January 1, 2024, security patches will no longer be    #
# provided for the following versions of Slackware (which will all #
# be more than 7 years old at that time):                          #
#   Slackware 14.0, Slackware 14.1, Slackware 14.2.                #
# If you are still running these versions you should consider      #
# migrating to a newer version (preferably as recent as possible). #
# Alternately, you may make arrangements to handle your own        #
# security patches.                                                #
####################################################################

Slackware 14.2 is EOL. Maybe it's easier to upgrade or rebuild that container to 15.0 than deal with Node.js issues

Thanks for the info.

The migration to SL15 is ongoing. I have containers for both 14.2 and 15 in a CI pipeline to be able to support both for the time being.
Was hoping to keep 14.2 around for a bit longer, but this dependency for Node.js looks like trouble.