from the very last lines of linking in src_compile: [...] /var/tmp/portage/net-libs/nodejs-14.15.4/work/node-v14.15.4/out/Release/obj.target/tools/v8_gypfiles/libv8_compiler.a /var/tmp/portage/net-libs/nodejs-14.15.4/work/node-v14.15.4/out/Release/obj.target/tools/v8_gypfiles/libv8_initializers.a -lz -luv -lbrotlidec -lbrotlienc -lcares -lnghttp2 -lcrypto -lssl -lm -ldl -Wl,--end-group rm 590f14ee06654dfb5028d9c92e51d2aa55485f86.intermediate 57f731c6787b3aa062120c4a361e72aefbaa0b38.intermediate fc2808e2ea2d7fc9bca2ff87fa2557e79f21b70d.intermediate if [ ! -r node -o ! -L node ]; then \ ln -fs out/Release/node node; fi /usr/bin/python3.8 tools/install.py install '/var/tmp/portage/net-libs/nodejs-14.15.4/image' '/usr' /usr/bin/env: ‘node’: No such file or directory >>> Completed installing net-libs/nodejs-14.15.4 into /var/tmp/portage/net-libs/nodejs-14.15.4/image * Final size of build directory: 1192136 KiB ( 1.1 GiB) * Final size of installed tree: 105144 KiB (102.6 MiB) strip: x86_64-pc-linux-gnu-strip --strip-unneeded -N __gentoo_check_ldflags__ -R .comment -R .GCC.command.line -R .note.gnu.gold-version /usr/bin/node I found this issue, seems to be related: https://github.com/nodejs/node-v0.x-archive/issues/3911 emerge -pv nodejs: [ebuild R ] net-libs/nodejs-14.15.4:0/14::gentoo USE="icu npm snapshot ssl system-ssl -debug -doc -inspector -pax_kernel -system-icu -systemtap -test" CPU_FLAGS_X86="sse2" 0 KiB the binary seems fine though, just wanted to leat maintainer know there is something quirky going on. if you need full build log please request it, nodejs demands too many cpu cycles to just provide a build.log for suche a seemingly minor issue.
I've seen it but thanks for the report anyway. From what I too say say this is indeed harmless, and actually letting this run would make things much more complicated for cross-compilation.