nvm install 18 (version >= 18.5.x) fails on i386 architecture

[ms270169]

Operating system and version:

Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
Architecture: i386

nvm debug output:

nvm --version: v0.39.1
$SHELL: /bin/bash
$SHLVL: 1
shell version: 'GNU bash, Version 5.1.4(1)-release (i686-pc-linux-gnu)'
uname -a: 'Linux 5.10.0-18-686-pae #1 SMP Debian 5.10.140-1 (2022-09-02) i686 GNU/Linux'
checksum binary: 'sha256sum'
OS version: Debian GNU/Linux 11  

nvm ls output:

->     v16.17.1
default -> 16 (-> v16.17.1)
iojs -> N/A (default)
unstable -> N/A (default)
node -> stable (-> v16.17.1) (default)
stable -> 16.17 (-> v16.17.1) (default)
lts/* -> lts/gallium (-> v16.17.1)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.24.1 (-> N/A)
lts/erbium -> v12.22.12 (-> N/A)
lts/fermium -> v14.20.1 (-> N/A)
lts/gallium -> v16.17.1

How did you install nvm?

install script in readme

What steps did you perform?

nvm install 18

What happened?

build fails

cc -o /home/xyz/.nvm/.cache/src/node-v18.9.1/files/out/Release/obj.target/openssl/deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.o op	86.S '-DV8_DEPRECATION_WARNINGS' '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_GLIBCXX_USE_CXX11_ABI=1' '-DNODE_OPENSSL_CONF_NAME=nodejs_conf' '-DNODE_OPENSSL_HAS_QUIC' '-D__STDC_FORMAT_MACROS' '-DOPENSSL_NO_PINSHARED' '-DOPENSSL_THREADS' '-DOPENSSL_NO_HW' '-DOPENSSL_API_COMPAT=0x10100001L' '-DSTATIC_LEGACY' '-DNDEBUG' '-DOPENSSL_USE_NODELETE' '-DL_ENDIAN' '-DOPENSSL_BUILDING_OPENSSL' '-DAES_ASM' '-DCMLL_ASM' '-DDES_ASM' '-DECP_NISTZ256_ASM' '-DGHASH_ASM' '-DMD5_ASM' '-DOPENSSL_BN_ASM_GF2m' '-DOPENSSL_BN_ASM_MONT' '-DOPENSSL_BN_ASM_PART_WORDS' '-DOPENSSL_CPUID_OBJ' '-DOPENSSL_IA32_SSE2' '-DPADLOCK_ASM' '-DPOLY1305_ASM' '-DRMD160_ASM' '-DSHA1_ASM' '-DSHA256_ASM' '-DSHA512_ASM' '-DVPAES_ASM' '-DWHIRLPOOL_ASM' '-DOPENSSL_PIC' '-DMODULESDIR="/home/xyz/.nvm/.cache/src/node-v18.9.1/files/out/Release/obj.target/deps/openssl/lib/openssl-modules"' '-DOPENSSLDIR="/etc/ssl"' '-DENGINESDIR="/dev/null"' '-DTERMIOS' -I../deps/openssl/openssl -I../deps/openssl/openssl/include -I../deps/openssl/openssl/crypto -I../deps/openssl/openssl/crypto/include -I../deps/openssl/openssl/crypto/modes -I../deps/openssl/openssl/crypto/ec/curve448 -I../deps/openssl/openssl/crypto/ec/curve448/arch_32 -I../deps/openssl/openssl/providers/common/include -I../deps/openssl/openssl/providers/implementations/include -I../deps/openssl/config -I../deps/openssl/config/archs/linux-elf/asm -I../deps/openssl/config/archs/linux-elf/asm/include -I../deps/openssl/config/archs/linux-elf/asm/crypto -I../deps/openssl/config/archs/linux-elf/asm/crypto/include/internal -I../deps/openssl/config/archs/linux-elf/asm/providers/common/include  -pthread -Wall -Wextra -Wno-unused-parameter -m32 -Wa,--noexecstack -Wall -O3 -fomit-frame-pointer -pthread -Wall -O3 -fomit-frame-pointer -Wno-missing-field-initializers -Wno-old-style-declaration -O3 -fno-omit-frame-pointer  -MMD -MF /home/xyz/.nvm/.cache/src/node-v18.9.1/files/out/Release/.deps//home/xyz/.nvm/.cache/src/node-v18.9.1/files/out/Release/obj.target/openssl/deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.o.d.raw   -c
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S: Assembler messages:
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:5: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:8: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:277: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:280: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:439: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:442: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:998: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:1001: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:1066: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:1069: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:1426: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:1429: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:1647: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:1650: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:2210: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:2213: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:2280: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:2283: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:2816: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:2819: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:3053: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:3056: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:3066: Error: junk at end of line, first unrecognized character is `%'
../deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.S:3069: Error: junk at end of line, first unrecognized character is `%'
make[1]: *** [deps/openssl/openssl.target.mk:1157: /home/xyz/.nvm/.cache/src/node-v18.9.1/files/out/Release/obj.target/openssl/deps/openssl/config/archs/linux-elf/asm/crypto/aes/aes-586.o] Fehler 1
make: *** [Makefile:113: node] Fehler 2
nvm: install v18.9.1 failed!

One of the error locations in file aes-586.S (line 5 to 8):

     %ifdef __CET__
.byte   243,15,30,251
     %endif

What did you expect to happen?

build succeeds
(like nvm install 16 which succeeds on same system)

Is there anything in any of your profile files that modifies the PATH?

No

[ljharb]

Is i386 a 32 bit arch? node hasn’t supported those since v10 iirc.

[ljharb]

Either way, if node 16 works but node 18 doesn’t, the implication is that node itself is what’s not building. I’d suggest filing an issue on node to help debug.

[ms270169]

The root of the problem is not caused by architecture, because build of node (version >= 18.5.0) fails on Debian i386 and amd64 systems. Nasm styled assembler statements %ifdef and %endif cause a build fail. When replacing them with #ifdef and #endif the build succeeds.

See also build of node >= v18.5.0 fails on Debian systems

Because nvm uses ready-to-use bundles for amd64 architecture, a build is not needed on such systems, and problem remains only on i386 architecture where a build is needed.

Up to node version 18.4.x there are no %ifdef and %endif statements in openssl sources, and therefore no building problems.

[ljharb]

OK, still sounds like an issue with node itself, and not nvm.

Closing in favor of nodejs/node#44822, unless there's something we can do about it besides modifying the node files directly.