too long lines were shrinked: [2967/3019] x86_64-pc-linux-gnu-g++ -MMD -MF obj/deps/googletest/src/gtest.gtest-port.o.d -D_GLIBCXX_USE_CXX11_ABI=1 -DNODE_OPENSSL_CONF_NAME=nodejs_conf -DNODE_OPENSSL_HAS_QUIC -DICU_NO_USER_DATA_OVERRIDE -D__STDC_FORMAT_MACROS -DOPENSSL_NO_PINSHARED -DOPENSSL_THREADS -DGTEST_HAS_POSIX_RE=0 -DGTEST [2968/3019] x86_64-pc-linux-gnu-g++ -MMD -MF obj/deps/googletest/src/gtest.gtest-test-part.o.d -D_GLIBCXX_USE_CXX11_ABI=1 -DNODE_OPENSSL_CONF_NAME=nodejs_conf -DNODE_OPENSSL_HAS_QUIC -DICU_NO_USER_DATA_OVERRIDE -D__STDC_FORMAT_MACROS -DOPENSSL_NO_PINSHARED -DOPENSSL_THREADS -DGTEST_HAS_POSIX_RE=0 -D [2969/3019] x86_64-pc-linux-gnu-g++ -Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,--defsym=__gentoo_check_ldflags__=0 -pthread -rdynamic -Wl,-z,noexecstack -Wl,--whole-archive obj/tools/v8_gypfiles/libv8_snapshot.a -Wl,--no-whole-archive -Wl,-z,relro -Wl,-z,now -Wl,--whole-archive,obj/deps FAILED: node_mksnapshot x86_64-pc-linux-gnu-g++ -Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs -Wl,--defsym=__gentoo_check_ldflags__=0 -pthread -rdynamic -Wl,-z,noexecstack -Wl,--whole-archive obj/tools/v8_gypfiles/libv8_snapshot.a -Wl,--no-whole-archive -Wl,-z,relro -Wl,-z,now -Wl,--whole-archive,obj/deps/openssl/lib /usr/libexec/gcc/x86_64-pc-linux-gnu/ld: obj/deps/ngtcp2/nghttp3/lib/nghttp3.nghttp3_http.o: in function `nghttp3_http_parse_priority': nghttp3_http.c:(.text+0x41): undefined reference to `sf_parser_init' /usr/libexec/gcc/x86_64-pc-linux-gnu/ld: nghttp3_http.c:(.text+0x5a): undefined reference to `sf_parser_dict' collect2: error: ld returned 1 exit status ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_systemd-20240521-083502 UNMASKED: <sys-devel/gcc-15.0.9999:15 Please re-assign to toolchain@ if you get a test failure in C, C++, or Fortran code which makes no sense. <dev-build/meson-9999 Please re-assign to ztrawhcse@ if you cannot reproduced it with regular meson. The attached etc.portage.tar.xz has all details. ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-15 * clang/llvm (if any): clang version 18.1.6 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/18/bin Configuration file: /etc/clang/x86_64-pc-linux-gnu-clang.cfg /usr/lib/llvm/18 18.1.6 Python 3.11.9 Available Ruby profiles: [1] ruby31 (with Rubygems) [2] ruby32 (with Rubygems) * [3] ruby33 (with Rubygems) Available Rust versions: [1] rust-bin-1.77.1 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 21.0.3_p9 [openjdk-bin-21] *) Eclipse Temurin JDK 8.412_p08 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 system-vm [2] openjdk-bin-21 The Glorious Glasgow Haskell Compilation System, version 9.2.8 php cli (if any): go version go1.22.3 linux/amd64 HEAD of ::gentoo commit 4c789c6fae8c97731778999e31138e339ddd7d2f Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Wed May 22 22:18:58 2024 +0000 2024-05-22 22:18:57 UTC emerge -qpvO net-libs/nodejs [ebuild N ] net-libs/nodejs-22.1.0 USE="corepack icu inspector snapshot ssl system-icu -debug -doc (-lto) -npm (-pax-kernel) -system-ssl -test" CPU_FLAGS_X86="sse2"
Created attachment 893985 [details] emerge-info.txt
Created attachment 893986 [details] emerge-history.txt
Created attachment 893987 [details] environment
Created attachment 893988 [details] etc.clang.tar.xz
Created attachment 893989 [details] etc.portage.tar.xz
Created attachment 893990 [details] net-libs:nodejs-22.1.0:20240522-232816.log.xz
Created attachment 893991 [details] qlist-info.txt
Created attachment 893992 [details] temp.tar.xz
Fixed upstream in https://github.com/nodejs/node/commit/e53cbb22c2a6be899d68bc4e91862ddcd7e6f367
I misunderstood context, link above is patch where bug was introduced. Possibly? Disregard previous comment.
Created attachment 897953 [details, diff] Build fix patch This patch fixes the build for me, but I haven't looked into reporting this to upstream yet. If someone else wishes to take the credit, feel free. :)
can confirm the proposed patch works!
