/var/log/portage/build/sys-libs/libutempter-1.2.1:20240813-225442.log

file_937888.txt (text/plain), 206.88 KB, created by Sam James on 2024-08-13 22:58:43 UTC

 * Package:    sys-libs/libutempter-1.2.1:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

>>> Unpacking source...
>>> Unpacking libutempter-1.2.1.tar.gz to /var/tmp/portage/sys-libs/libutempter-1.2.1/work
>>> Source unpacked in /var/tmp/portage/sys-libs/libutempter-1.2.1/work
>>> Preparing source in /var/tmp/portage/sys-libs/libutempter-1.2.1/work/libutempter-1.2.1 ...
 * SED: some expressions in the following did not cause any changes
 *     sed -i "${args[@]}" Makefile || die
 * no-op: -e /^CFLAGS = $(RPM_OPT_FLAGS)/d
 * no-op: -e /^includedir /s:/usr/include:/usr/include:
 * no-op: -e /^mandir /s:=.*:= /usr/share/man:
>>> Source prepared.
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
>>> Configuring source in /var/tmp/portage/sys-libs/libutempter-1.2.1/work/libutempter-1.2.1 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/sys-libs/libutempter-1.2.1/work/libutempter-1.2.1 ...
make -j32 -l32 LDLIBS= 
x86_64-pc-linux-gnu-gcc -W -Wall -Waggregate-return -Wcast-align -Wconversion -Wdisabled-optimization -Wmissing-declarations -Wmissing-format-attribute -Wmissing-noreturn -Wmissing-prototypes -Wpointer-arith -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings -O3 -march=native -mtls-dialect=gnu2 -flto=jobserver -fno-semantic-interposition -pipe -fcf-protection=none -fdiagnostics-color=always -fdiagnostics-urls=never -frecord-gcc-switches -Wa,-O2 -Wa,-mtune=znver2  -Wstrict-aliasing -Wfree-nonheap-object -Werror=lto-type-mismatch -Werror=strict-aliasing -Werror=odr -Wstrict-aliasing -Wfree-nonheap-object -Werror=lto-type-mismatch -Werror=strict-aliasing -Werror=odr -Wbuiltin-declaration-mismatch -ggdb3 -Wformat -Wformat-security -Waddress -Warray-bounds -Wfree-nonheap-object -Wint-to-pointer-cast -Wmain -Wnonnull -Wodr -Wpointer-arith -Wpointer-to-int-cast -Wreturn-type -Wsizeof-pointer-memaccess -Wstrict-aliasing -Wstring-compare -Wuninitialized -Wmaybe-uninitialized -Wstringop-overflow -Wstringop-overread -Wstringop-truncation -Wdangling-pointer -Wformat-overflow -Wformat-truncation -Wuse-after-free -Wvarargs  -std=gnu99  -DLIBEXECDIR=\"/usr/lib64/misc\"  -Wl,-z,relro  -Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs -flto=jobserver -fuse-ld=mold -Wl,--defsym=__gentoo_check_ldflags__=0  -fPIE -pie -Wl,-z,now  utempter.c -o utempter
x86_64-pc-linux-gnu-gcc -W -Wall -Waggregate-return -Wcast-align -Wconversion -Wdisabled-optimization -Wmissing-declarations -Wmissing-format-attribute -Wmissing-noreturn -Wmissing-prototypes -Wpointer-arith -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings -O3 -march=native -mtls-dialect=gnu2 -flto=jobserver -fno-semantic-interposition -pipe -fcf-protection=none -fdiagnostics-color=always -fdiagnostics-urls=never -frecord-gcc-switches -Wa,-O2 -Wa,-mtune=znver2  -Wstrict-aliasing -Wfree-nonheap-object -Werror=lto-type-mismatch -Werror=strict-aliasing -Werror=odr -Wstrict-aliasing -Wfree-nonheap-object -Werror=lto-type-mismatch -Werror=strict-aliasing -Werror=odr -Wbuiltin-declaration-mismatch -ggdb3 -Wformat -Wformat-security -Waddress -Warray-bounds -Wfree-nonheap-object -Wint-to-pointer-cast -Wmain -Wnonnull -Wodr -Wpointer-arith -Wpointer-to-int-cast -Wreturn-type -Wsizeof-pointer-memaccess -Wstrict-aliasing -Wstring-compare -Wuninitialized -Wmaybe-uninitialized -Wstringop-overflow -Wstringop-overread -Wstringop-truncation -Wdangling-pointer -Wformat-overflow -Wformat-truncation -Wuse-after-free -Wvarargs  -std=gnu99  -DLIBEXECDIR=\"/usr/lib64/misc\"   -c -fPIC iface.c -o iface.os
x86_64-pc-linux-gnu-gcc -Wl,-z,relro  -Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs -flto=jobserver -fuse-ld=mold -Wl,--defsym=__gentoo_check_ldflags__=0  -shared \
	-Wl,-soname,libutempter.so.0,--version-script=libutempter.map,-z,defs \
	-lc iface.os -o libutempter.so
>>> Source compiled.
>>> Test phase [not enabled]: sys-libs/libutempter-1.2.1

>>> Install sys-libs/libutempter-1.2.1 into /var/tmp/portage/sys-libs/libutempter-1.2.1/image
make -j32 -l32 DESTDIR=/var/tmp/portage/sys-libs/libutempter-1.2.1/image install 
mkdir -p /var/tmp/portage/sys-libs/libutempter-1.2.1/image/usr/lib64 /var/tmp/portage/sys-libs/libutempter-1.2.1/image/usr/lib64/misc/utempter \
	/var/tmp/portage/sys-libs/libutempter-1.2.1/image/usr/include /var/tmp/portage/sys-libs/libutempter-1.2.1/image/usr/share/man/man3
install -p -m2711 utempter /var/tmp/portage/sys-libs/libutempter-1.2.1/image/usr/lib64/misc/utempter/
install -p -m644 utempter.h /var/tmp/portage/sys-libs/libutempter-1.2.1/image/usr/include/
install -p -m755 libutempter.so /var/tmp/portage/sys-libs/libutempter-1.2.1/image/usr/lib64/libutempter.so.1.2.1
ln -s libutempter.so.1.2.1 /var/tmp/portage/sys-libs/libutempter-1.2.1/image/usr/lib64/libutempter.so.0
ln -s libutempter.so.0 /var/tmp/portage/sys-libs/libutempter-1.2.1/image/usr/lib64/libutempter.so
install -p -m644 utempter.3 /var/tmp/portage/sys-libs/libutempter-1.2.1/image/usr/share/man/man3/
for n in libutempter utempter_add_record utempter_remove_record \
    utempter_remove_added_record utempter_set_helper; do \
	ln -s utempter.3 /var/tmp/portage/sys-libs/libutempter-1.2.1/image/usr/share/man/man3/$n.3; \
done
>>> Completed installing sys-libs/libutempter-1.2.1 into /var/tmp/portage/sys-libs/libutempter-1.2.1/image

grep: **/*.am: No such file or directory
 * Final size of build directory: 432 KiB
 * Final size of installed tree:  232 KiB

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/lib64/libutempter.so.1.2.1
   /usr/lib64/misc/utempter/utempter
installsources: rsyncing source files
>>> Done.
/usr/bin/python3.13: can't open file '/var/tmp/portage/._portage_reinstall_._75lho_q/bin/pid-ns-init': [Errno 2] No such file or directory
/usr/bin/python3.13: can't open file '/var/tmp/portage/._portage_reinstall_._75lho_q/bin/pid-ns-init': [Errno 2] No such file or directory
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
/bin/bash: line 1: /var/tmp/portage/._portage_reinstall_._75lho_q/bin/misc-functions.sh: No such file or directory
 * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
!!! instprep failed
/bin/bash: line 1: /var/tmp/portage/._portage_reinstall_._75lho_q/bin/misc-functions.sh: No such file or directory
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package x11-libs/pixman-0.43.4:
 * Log file: /var/log/portage/build/x11-libs/pixman-0.43.4:20240813-224639.log

 * Package:    x11-libs/pixman-0.43.4:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 cpu_flags_x86_mmxext cpu_flags_x86_sse2 cpu_flags_x86_ssse3 elibc_glibc kernel_linux test
 * FEATURES:   network-sandbox preserve-libs sandbox test userpriv usersandbox

 * Messages for package app-crypt/libb2-0.98.1-r3:
 * Log file: /var/log/portage/build/app-crypt/libb2-0.98.1-r3:20240813-224640.log

 * Package:    app-crypt/libb2-0.98.1-r3:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux openmp
 * FEATURES:   network-sandbox preserve-libs sandbox test userpriv usersandbox

 * Messages for package dev-libs/gmp-6.3.0-r1:
 * Log file: /var/log/portage/build/dev-libs/gmp-6.3.0-r1:20240813-224641.log

 * Package:    dev-libs/gmp-6.3.0-r1:0/10.4
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 asm cxx elibc_glibc kernel_linux pic
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox

 * Messages for package dev-libs/libgcrypt-1.11.0:
 * Log file: /var/log/portage/build/dev-libs/libgcrypt-1.11.0:20240813-224641.log

 * Package:    dev-libs/libgcrypt-1.11.0:0/20
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 asm cpu_flags_x86_aes cpu_flags_x86_avx cpu_flags_x86_avx2 cpu_flags_x86_sha cpu_flags_x86_sse4_1 elibc_glibc getentropy kernel_linux verify-sig
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux-6.6.45
 * Found kernel object directory:
 *     /usr/src/linux-6.6.45
 * Found sources for kernel version:
 *     6.6.45

 * Messages for package net-libs/libpsl-0.21.5:
 * Log file: /var/log/portage/build/net-libs/libpsl-0.21.5:20240813-224642.log

 * Package:    net-libs/libpsl-0.21.5:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc icu idn kernel_linux test
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox
 * "icu" and "idn" USE flags are enabled. Using "idn".

 * Messages for package sys-libs/glibc-2.40:
 * Log file: /var/log/portage/build/sys-libs/glibc-2.40:20240813-224643.log

 * Package:    sys-libs/glibc-2.40:2.2
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 caps elibc_glibc kernel_linux multiarch multilib ssp stack-realign static-libs systemd test
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox

 * Messages for package sys-libs/libxcrypt-4.4.36-r3:
 * Log file: /var/log/portage/build/sys-libs/libxcrypt-4.4.36-r3:20240813-224644.log

 * Package:    sys-libs/libxcrypt-4.4.36-r3:0/1
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 compat elibc_glibc kernel_linux static-libs system test
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox

 * Messages for package sys-libs/gpm-1.20.7-r6:
 * Log file: /var/log/portage/build/sys-libs/gpm-1.20.7-r6:20240813-224644.log

 * Package:    sys-libs/gpm-1.20.7-r6:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     6.6.45
 * Checking for suitable kernel configuration options ...

 * Messages for package dev-lang/perl-5.40.0:
 * Log file: /var/log/portage/build/dev-lang/perl-5.40.0:20240813-224645.log

 * Package:    dev-lang/perl-5.40.0:0/5.40
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc gdbm kernel_linux
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox

 * Messages for package dev-python/pypy3_10-exe-7.3.16:
 * Log file: /var/log/portage/build/dev-python/pypy3_10-exe-7.3.16:20240813-224646.log

 * Package:    dev-python/pypy3_10-exe-7.3.16:7.3.16
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 cpu_flags_x86_sse2 elibc_glibc jit kernel_linux ncurses
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Checking for at least 6 GiB RAM ...

 * Messages for package sys-devel/gettext-0.22.5:
 * Log file: /var/log/portage/build/sys-devel/gettext-0.22.5:20240813-224647.log

 * Package:    sys-devel/gettext-0.22.5:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 acl amd64 cxx elibc_glibc emacs kernel_linux ncurses nls openmp verify-sig xattr
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox

 * Messages for package media-libs/freetype-2.13.3:
 * Log file: /var/log/portage/build/media-libs/freetype-2.13.3:20240813-224648.log

 * Package:    media-libs/freetype-2.13.3:2
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        X abi_x86_32 abi_x86_64 adobe-cff amd64 bzip2 cleartype-hinting elibc_glibc harfbuzz kernel_linux png svg
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * The "svg" USE flag only has effect when the "utils" USE flag is also enabled.

 * Messages for package sys-apps/util-linux-2.40.2:
 * Log file: /var/log/portage/build/sys-apps/util-linux-2.40.2:20240813-224648.log

 * Package:    sys-apps/util-linux-2.40.2:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 caps cramfs elibc_glibc hardlink kernel_linux logger ncurses nls pam python_targets_python3_10 python_targets_python3_11 python_targets_python3_12 readline su suid systemd test udev unicode verify-sig
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox

 * Messages for package dev-lang/python-3.10.14_p2:
 * Log file: /var/log/portage/build/dev-lang/python-3.10.14_p2:20240813-224649.log

 * Package:    dev-lang/python-3.10.14_p2:3.10
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 bluetooth elibc_glibc ensurepip gdbm kernel_linux ncurses pgo readline sqlite ssl test valgrind verify-sig
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox
 * Checking for at least 5500 MiB disk space at "/var/tmp/portage/dev-lang/python-3.10.14_p2/temp" ...

 * Messages for package dev-lang/python-3.11.9_p1:
 * Log file: /var/log/portage/build/dev-lang/python-3.11.9_p1:20240813-224650.log

 * Package:    dev-lang/python-3.11.9_p1:3.11
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 bluetooth elibc_glibc ensurepip gdbm kernel_linux ncurses pgo readline sqlite ssl test valgrind verify-sig
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox
 * Checking for at least 5500 MiB disk space at "/var/tmp/portage/dev-lang/python-3.11.9_p1/temp" ...

 * Messages for package dev-lang/python-3.12.5:
 * Log file: /var/log/portage/build/dev-lang/python-3.12.5:20240813-224651.log

 * Package:    dev-lang/python-3.12.5:3.12
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 bluetooth elibc_glibc ensurepip gdbm kernel_linux ncurses pgo readline sqlite ssl test valgrind verify-sig
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox
 * Checking for at least 5500 MiB disk space at "/var/tmp/portage/dev-lang/python-3.12.5/temp" ...

 * Messages for package sys-apps/systemd-256.4:
 * Log file: /var/log/portage/build/sys-apps/systemd-256.4:20240813-224651.log

 * Package:    sys-apps/systemd-256.4:0/2
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 acl amd64 boot cryptsetup curl dns-over-tls elfutils elibc_glibc gcrypt homed importd kernel-install kernel_linux kmod lz4 lzma openssl pam pcre policykit python_single_target_python3_12 resolvconf seccomp sysv-utils tpm ukify xkb zstd
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     6.6.45
 * Checking for suitable kernel configuration options ...

 * Messages for package dev-lang/python-3.13.0_rc1_p1:
 * Log file: /var/log/portage/build/dev-lang/python-3.13.0_rc1_p1:20240813-224653.log

 * Package:    dev-lang/python-3.13.0_rc1_p1:3.13
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 bluetooth debug elibc_glibc ensurepip gdbm gil kernel_linux llvm_slot_18 ncurses pgo readline sqlite ssl test valgrind verify-sig
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox
 * Checking for at least 5500 MiB disk space at "/var/tmp/portage/dev-lang/python-3.13.0_rc1_p1/temp" ...

 * Messages for package media-libs/mesa-24.2.0_rc4:
 * Log file: /var/log/portage/build/media-libs/mesa-24.2.0_rc4:20240813-224654.log

 * Package:    media-libs/mesa-24.2.0_rc4:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        X abi_x86_32 abi_x86_64 amd64 cpu_flags_x86_sse2 elibc_glibc kernel_linux llvm llvm_slot_18 opengl proprietary-codecs valgrind video_cards_radeon video_cards_radeonsi vulkan wayland zstd
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

 * Messages for package app-text/mandoc-1.14.6:
 * Log file: /var/log/portage/build/app-text/mandoc-1.14.6:20240813-224655.log

 * Package:    app-text/mandoc-1.14.6:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

 * Messages for package dev-libs/botan-3.2.0-r2:
 * Log file: /var/log/portage/build/dev-libs/botan-3.2.0-r2:20240813-224655.log

 * Package:    dev-libs/botan-3.2.0-r2:3/3.2
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 bzip2 cpu_flags_x86_aes cpu_flags_x86_avx2 cpu_flags_x86_popcnt cpu_flags_x86_rdrand cpu_flags_x86_sha cpu_flags_x86_sse2 cpu_flags_x86_sse4_1 cpu_flags_x86_sse4_2 cpu_flags_x86_ssse3 elibc_glibc kernel_linux python_targets_python3_10 python_targets_python3_11 python_targets_python3_12 test verify-sig zlib
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox

 * Messages for package net-dns/dnsmasq-2.90:
 * Log file: /var/log/portage/build/net-dns/dnsmasq-2.90:20240813-224656.log

 * Package:    net-dns/dnsmasq-2.90:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 dbus dhcp dumpfile elibc_glibc inotify ipv6 kernel_linux loop lua_single_target_lua5-1 nls script
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

 * Messages for package sci-libs/fftw-3.3.10:
 * Log file: /var/log/portage/build/sci-libs/fftw-3.3.10:20240813-224657.log

 * Package:    sci-libs/fftw-3.3.10:3.0/3
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 cpu_flags_x86_avx cpu_flags_x86_avx2 cpu_flags_x86_fma3 cpu_flags_x86_sse cpu_flags_x86_sse2 elibc_glibc kernel_linux openmp test
 * FEATURES:   network-sandbox preserve-libs sandbox test userpriv usersandbox

 * Messages for package sys-apps/pciutils-3.13.0:
 * Log file: /var/log/portage/build/sys-apps/pciutils-3.13.0:20240813-224657.log

 * Package:    sys-apps/pciutils-3.13.0:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux kmod udev zlib
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package sys-libs/libomp-18.1.8:
 * Log file: /var/log/portage/build/sys-libs/libomp-18.1.8:20240813-224658.log

 * Package:    sys-libs/libomp-18.1.8:0/18.1
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux llvm_targets_AMDGPU llvm_targets_NVPTX python_single_target_python3_12 verify-sig
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     6.6.45

 * Messages for package x11-drivers/xf86-video-ati-22.0.0:
 * Log file: /var/log/portage/build/x11-drivers/xf86-video-ati-22.0.0:20240813-224659.log

 * Package:    x11-drivers/xf86-video-ati-22.0.0:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux udev
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     6.6.45
 * Checking for suitable kernel configuration options ...

 * Messages for package cross-aarch64_be-unknown-linux-gnu/gcc-14.2.0:
 * Log file: /var/log/portage/build/cross-aarch64_be-unknown-linux-gnu/gcc-14.2.0:20240813-224700.log

 * Package:    cross-aarch64_be-unknown-linux-gnu/gcc-14.2.0:14
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 cxx elibc_glibc kernel_linux pie ssp valgrind
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package cross-aarch64-unknown-linux-gnu/gcc-14.2.0:
 * Log file: /var/log/portage/build/cross-aarch64-unknown-linux-gnu/gcc-14.2.0:20240813-224701.log

 * Package:    cross-aarch64-unknown-linux-gnu/gcc-14.2.0:14
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 cxx elibc_glibc kernel_linux pie ssp valgrind
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package cross-arm-none-eabi/gcc-14.2.0:
 * Log file: /var/log/portage/build/cross-arm-none-eabi/gcc-14.2.0:20240813-224702.log

 * Package:    cross-arm-none-eabi/gcc-14.2.0:14
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux multilib valgrind
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package cross-armv6j-unknown-linux-musleabihf/gcc-14.2.0:
 * Log file: /var/log/portage/build/cross-armv6j-unknown-linux-musleabihf/gcc-14.2.0:20240813-224702.log

 * Package:    cross-armv6j-unknown-linux-musleabihf/gcc-14.2.0:14
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 cxx elibc_glibc kernel_linux pie ssp valgrind
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package cross-armv7a-unknown-linux-gnueabihf/gcc-13.3.1_p20240614:
 * Log file: /var/log/portage/build/cross-armv7a-unknown-linux-gnueabihf/gcc-13.3.1_p20240614:20240813-224703.log

 * Package:    cross-armv7a-unknown-linux-gnueabihf/gcc-13.3.1_p20240614:13
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 cxx elibc_glibc kernel_linux pie ssp valgrind
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package cross-armv7a-unknown-linux-musleabihf/gcc-14.2.0:
 * Log file: /var/log/portage/build/cross-armv7a-unknown-linux-musleabihf/gcc-14.2.0:20240813-224704.log

 * Package:    cross-armv7a-unknown-linux-musleabihf/gcc-14.2.0:14
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 cxx elibc_glibc kernel_linux pie ssp valgrind
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package cross-hppa2.0-unknown-linux-gnu/gcc-14.2.0:
 * Log file: /var/log/portage/build/cross-hppa2.0-unknown-linux-gnu/gcc-14.2.0:20240813-224705.log

 * Package:    cross-hppa2.0-unknown-linux-gnu/gcc-14.2.0:14
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 cxx elibc_glibc kernel_linux pie valgrind
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package cross-hppa64-unknown-linux-gnu/gcc-14.2.0:
 * Log file: /var/log/portage/build/cross-hppa64-unknown-linux-gnu/gcc-14.2.0:20240813-224705.log

 * Package:    cross-hppa64-unknown-linux-gnu/gcc-14.2.0:14
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux pie valgrind
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package cross-powerpc64le-unknown-linux-gnu/gcc-14.2.0:
 * Log file: /var/log/portage/build/cross-powerpc64le-unknown-linux-gnu/gcc-14.2.0:20240813-224706.log

 * Package:    cross-powerpc64le-unknown-linux-gnu/gcc-14.2.0:14
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 cxx elibc_glibc kernel_linux pie ssp valgrind
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package cross-powerpc64-unknown-linux-gnu/gcc-14.2.0:
 * Log file: /var/log/portage/build/cross-powerpc64-unknown-linux-gnu/gcc-14.2.0:20240813-224707.log

 * Package:    cross-powerpc64-unknown-linux-gnu/gcc-14.2.0:14
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 cxx elibc_glibc kernel_linux pie ssp valgrind
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package cross-powerpc-unknown-linux-gnu/gcc-14.2.0:
 * Log file: /var/log/portage/build/cross-powerpc-unknown-linux-gnu/gcc-14.2.0:20240813-224707.log

 * Package:    cross-powerpc-unknown-linux-gnu/gcc-14.2.0:14
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 cxx elibc_glibc kernel_linux pie ssp valgrind
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package cross-s390-ibm-linux-gnu/gcc-14.2.0:
 * Log file: /var/log/portage/build/cross-s390-ibm-linux-gnu/gcc-14.2.0:20240813-224708.log

 * Package:    cross-s390-ibm-linux-gnu/gcc-14.2.0:14
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 cxx elibc_glibc kernel_linux pie ssp valgrind
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package cross-sparc64-unknown-linux-gnu/gcc-14.2.0:
 * Log file: /var/log/portage/build/cross-sparc64-unknown-linux-gnu/gcc-14.2.0:20240813-224709.log

 * Package:    cross-sparc64-unknown-linux-gnu/gcc-14.2.0:14
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 cet cxx elibc_glibc fortran graphite hardened jit kernel_linux nls openmp pie ssp valgrind
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package dev-qt/qtcore-5.15.14:
 * Log file: /var/log/portage/build/dev-qt/qtcore-5.15.14:20240813-224710.log

 * Package:    dev-qt/qtcore-5.15.14:5/5.15.14
 * Repository: gentoo
 * Maintainer: [e-mail]
 * Upstream:   https://bugreports.qt.io/
 * USE:        abi_x86_64 amd64 elibc_glibc icu kernel_linux
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux-6.6.45
 * Found kernel object directory:
 *     /usr/src/linux-6.6.45
 * Found sources for kernel version:
 *     6.6.45

 * Messages for package media-gfx/graphicsmagick-1.3.43-r1:
 * Log file: /var/log/portage/build/media-gfx/graphicsmagick-1.3.43-r1:20240813-224710.log

 * Package:    media-gfx/graphicsmagick-1.3.43-r1:0/1.3
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * USE:        X abi_x86_64 amd64 bzip2 cxx elibc_glibc imagemagick jpeg kernel_linux lcms openmp png tiff truetype verify-sig zlib
 * FEATURES:   network-sandbox preserve-libs sandbox test userpriv usersandbox

 * Messages for package sys-fs/fuse-overlayfs-1.13:
 * Log file: /var/log/portage/build/sys-fs/fuse-overlayfs-1.13:20240813-224711.log

 * Package:    sys-fs/fuse-overlayfs-1.13:0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail],[e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     6.6.45

 * Messages for package www-apps/hugo-0.129.0:
 * Log file: /var/log/portage/build/www-apps/hugo-0.129.0:20240813-224712.log

 * Package:    www-apps/hugo-0.129.0:0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc extended kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Checking for at least 1500 MiB disk space at "/var/tmp/portage/www-apps/hugo-0.129.0/temp" ...

 * Messages for package cross-aarch64_be-unknown-linux-gnu/glibc-2.40:
 * Log file: /var/log/portage/build/cross-aarch64_be-unknown-linux-gnu/glibc-2.40:20240813-224713.log

 * Package:    cross-aarch64_be-unknown-linux-gnu/glibc-2.40:2.2
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 caps elibc_glibc kernel_linux multiarch ssp static-libs systemd
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

 * Messages for package cross-aarch64-unknown-linux-gnu/glibc-2.40:
 * Log file: /var/log/portage/build/cross-aarch64-unknown-linux-gnu/glibc-2.40:20240813-224713.log

 * Package:    cross-aarch64-unknown-linux-gnu/glibc-2.40:2.2
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 caps elibc_glibc kernel_linux multiarch ssp static-libs systemd
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

 * Messages for package cross-armv7a-unknown-linux-gnueabihf/glibc-2.39-r6:
 * Log file: /var/log/portage/build/cross-armv7a-unknown-linux-gnueabihf/glibc-2.39-r6:20240813-224714.log

 * Package:    cross-armv7a-unknown-linux-gnueabihf/glibc-2.39-r6:2.2
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 caps elibc_glibc kernel_linux multiarch ssp static-libs systemd
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

 * Messages for package cross-hppa2.0-unknown-linux-gnu/glibc-2.40:
 * Log file: /var/log/portage/build/cross-hppa2.0-unknown-linux-gnu/glibc-2.40:20240813-224715.log

 * Package:    cross-hppa2.0-unknown-linux-gnu/glibc-2.40:2.2
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 caps elibc_glibc kernel_linux multiarch ssp static-libs systemd
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

 * Messages for package cross-powerpc64le-unknown-linux-gnu/glibc-2.40:
 * Log file: /var/log/portage/build/cross-powerpc64le-unknown-linux-gnu/glibc-2.40:20240813-224716.log

 * Package:    cross-powerpc64le-unknown-linux-gnu/glibc-2.40:2.2
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 caps elibc_glibc kernel_linux multiarch ssp static-libs systemd
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

 * Messages for package cross-powerpc64-unknown-linux-gnu/glibc-2.40:
 * Log file: /var/log/portage/build/cross-powerpc64-unknown-linux-gnu/glibc-2.40:20240813-224716.log

 * Package:    cross-powerpc64-unknown-linux-gnu/glibc-2.40:2.2
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 caps elibc_glibc kernel_linux multiarch ssp static-libs systemd
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

 * Messages for package cross-powerpc-unknown-linux-gnu/glibc-2.40:
 * Log file: /var/log/portage/build/cross-powerpc-unknown-linux-gnu/glibc-2.40:20240813-224717.log

 * Package:    cross-powerpc-unknown-linux-gnu/glibc-2.40:2.2
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 caps elibc_glibc kernel_linux multiarch ssp static-libs systemd
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

 * Messages for package cross-s390-ibm-linux-gnu/glibc-2.40:
 * Log file: /var/log/portage/build/cross-s390-ibm-linux-gnu/glibc-2.40:20240813-224718.log

 * Package:    cross-s390-ibm-linux-gnu/glibc-2.40:2.2
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 caps elibc_glibc kernel_linux multiarch ssp static-libs systemd
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

 * Messages for package cross-sparc64-unknown-linux-gnu/glibc-2.40:
 * Log file: /var/log/portage/build/cross-sparc64-unknown-linux-gnu/glibc-2.40:20240813-224719.log

 * Package:    cross-sparc64-unknown-linux-gnu/glibc-2.40:2.2
 * Repository: crossdev
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 caps elibc_glibc kernel_linux multiarch ssp static-libs systemd
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

 * Messages for package net-wireless/hostapd-2.10-r3:
 * Log file: /var/log/portage/build/net-wireless/hostapd-2.10-r3:20240813-224719.log

 * Package:    net-wireless/hostapd-2.10-r3:0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc ipv6 kernel_linux suiteb wps
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package net-libs/nodejs-22.6.0:
 * Log file: /var/log/portage/build/net-libs/nodejs-22.6.0:20240813-224720.log

 * Package:    net-libs/nodejs-22.6.0:0/22
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 cpu_flags_x86_sse2 elibc_glibc icu inspector kernel_linux npm snapshot ssl system-icu system-ssl
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

 * Messages for package net-misc/openssh-9.8_p1-r2:
 * Log file: /var/log/portage/build/net-misc/openssh-9.8_p1-r2:20240813-224721.log

 * Package:    net-misc/openssh-9.8_p1-r2:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux pam pie ssl verify-sig
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package sys-devel/mold-2.33.0:
 * Log file: /var/log/portage/build/sys-devel/mold-2.33.0:20240813-224722.log

 * Package:    sys-devel/mold-2.33.0:0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox

 * Messages for package x11-drivers/xf86-input-libinput-1.4.0:
 * Log file: /var/log/portage/build/x11-drivers/xf86-input-libinput-1.4.0:20240813-224722.log

 * Package:    x11-drivers/xf86-input-libinput-1.4.0:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     6.6.45
 * Checking for suitable kernel configuration options ...

 * Messages for package sys-apps/portage-9999:
 * Log file: /var/log/portage/build/sys-apps/portage-9999:20240813-224723.log

 * Package:    sys-apps/portage-9999:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * Upstream:   [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc ipc kernel_linux native-extensions python_targets_pypy3 python_targets_python3_10 python_targets_python3_11 python_targets_python3_12 python_targets_python3_13 rsync-verify xattr
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     6.6.45
 * Checking for suitable kernel configuration options ...

 * Messages for package dev-util/perf-6.10.4:
 * Log file: /var/log/portage/build/dev-util/perf-6.10.4:20240813-224724.log

 * Package:    dev-util/perf-6.10.4:0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail],[e-mail]
 * USE:        abi_x86_64 amd64 caps crypt doc elibc_glibc gtk kernel_linux libtraceevent libtracefs python_targets_python3_10 python_targets_python3_11 python_targets_python3_12 python_targets_python3_13
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

 * Messages for package sys-libs/compiler-rt-17.0.6:
 * Log file: /var/log/portage/build/sys-libs/compiler-rt-17.0.6:20240813-224725.log

 * Package:    sys-libs/compiler-rt-17.0.6:17
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 clang elibc_glibc kernel_linux verify-sig
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package sys-libs/compiler-rt-18.1.8:
 * Log file: /var/log/portage/build/sys-libs/compiler-rt-18.1.8:20240813-224726.log

 * Package:    sys-libs/compiler-rt-18.1.8:18
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 clang elibc_glibc kernel_linux verify-sig
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package sys-libs/compiler-rt-sanitizers-17.0.6:
 * Log file: /var/log/portage/build/sys-libs/compiler-rt-sanitizers-17.0.6:20240813-224727.log

 * Package:    sys-libs/compiler-rt-sanitizers-17.0.6:17
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 asan cfi clang dfsan elibc_glibc gwp-asan hwasan kernel_linux libfuzzer lsan memprof msan profile safestack scudo tsan ubsan verify-sig xray
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package sys-libs/compiler-rt-sanitizers-18.1.8:
 * Log file: /var/log/portage/build/sys-libs/compiler-rt-sanitizers-18.1.8:20240813-224727.log

 * Package:    sys-libs/compiler-rt-sanitizers-18.1.8:18
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 asan cfi clang dfsan elibc_glibc gwp-asan hwasan kernel_linux libfuzzer lsan memprof msan profile safestack scudo tsan ubsan verify-sig xray
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package kde-frameworks/kirigami-5.116.0:
 * Log file: /var/log/portage/build/kde-frameworks/kirigami-5.116.0:20240813-224728.log

 * Package:    kde-frameworks/kirigami-5.116.0:5/5.116
 * Repository: gentoo
 * Maintainer: [e-mail]
 * Upstream:   https://bugs.kde.org/
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux openmp
 * FEATURES:   ccache compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package kde-frameworks/kirigami-6.5.0:
 * Log file: /var/log/portage/build/kde-frameworks/kirigami-6.5.0:20240813-224729.log

 * Package:    kde-frameworks/kirigami-6.5.0:6/6.5
 * Repository: gentoo
 * Maintainer: [e-mail]
 * Upstream:   https://bugs.kde.org/
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux openmp
 * FEATURES:   ccache compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package media-libs/libmypaint-1.6.1-r3:
 * Log file: /var/log/portage/build/media-libs/libmypaint-1.6.1-r3:20240813-224730.log

 * Package:    media-libs/libmypaint-1.6.1-r3:0/0.0.0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux nls openmp
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox

 * Messages for package app-emulation/qemu-9.0.2:
 * Log file: /var/log/portage/build/app-emulation/qemu-9.0.2:20240813-224730.log

 * Package:    app-emulation/qemu-9.0.2:0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * USE:        abi_x86_64 aio alsa amd64 bzip2 curl elibc_glibc fdt filecaps gnutls gtk jpeg kernel_linux ncurses nls opengl oss pam pin-upstream-blobs pipewire png pulseaudio python_targets_python3_10 python_targets_python3_11 python_targets_python3_12 qemu_softmmu_targets_i386 qemu_softmmu_targets_x86_64 qemu_user_targets_aarch64 qemu_user_targets_aarch64_be qemu_user_targets_alpha qemu_user_targets_armeb qemu_user_targets_hppa qemu_user_targets_i386 qemu_user_targets_m68k qemu_user_targets_ppc qemu_user_targets_ppc64 qemu_user_targets_ppc64le qemu_user_targets_sparc qemu_user_targets_sparc64 qemu_user_targets_x86_64 sdl seccomp slirp spice static-user udev usb usbredir vhost-net vnc xattr
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     6.6.45
 * Checking for suitable kernel configuration options ...

 * Messages for package www-client/firefox-129.0:
 * Log file: /var/log/portage/build/www-client/firefox-129.0:20240813-224732.log

 * Package:    www-client/firefox-129.0:rapid
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        X abi_x86_64 amd64 clang dbus elibc_glibc hardened jumbo-build kernel_linux l10n_en-GB llvm_slot_18 lto pulseaudio system-av1 system-harfbuzz system-icu system-jpeg system-libevent system-libvpx system-webp telemetry wayland
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Checking for at least 13500 MiB disk space at "/var/tmp/portage/www-client/firefox-129.0/temp" ...

 * Messages for package media-libs/opencv-4.9.0-r1:
 * Log file: /var/log/portage/build/media-libs/opencv-4.9.0-r1:20240813-224732.log

 * Package:    media-libs/opencv-4.9.0-r1:0/4.9.0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 contrib contribdnn cpu_flags_x86_avx cpu_flags_x86_avx2 cpu_flags_x86_f16c cpu_flags_x86_fma3 cpu_flags_x86_popcnt cpu_flags_x86_sse cpu_flags_x86_sse2 cpu_flags_x86_sse3 cpu_flags_x86_sse4_1 cpu_flags_x86_sse4_2 cpu_flags_x86_ssse3 eigen elibc_glibc features2d ffmpeg jpeg kernel_linux opengl openmp png python_targets_python3_10 python_targets_python3_11 python_targets_python3_12 qt5 tiff
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox

 * Messages for package sys-fs/bees-0.10-r1:
 * Log file: /var/log/portage/build/sys-fs/bees-0.10-r1:20240813-224733.log

 * Package:    sys-fs/bees-0.10-r1:0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * Upstream:   https://github.com/Zygo/bees/issues
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     6.6.45
 * Bees recommends running the latest current kernel for performance and
 * reliability reasons, see README.md.

 * Messages for package app-admin/entr-5.6:
 * Log file: /var/log/portage/build/app-admin/entr-5.6:20240813-224734.log

 * Package:    app-admin/entr-5.6:0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * ./configure
 * Skipping make test/check due to ebuild restriction.
 * Final size of build directory: 296 KiB
 * Final size of installed tree:   68 KiB

 * Messages for package app-crypt/argon2-20190702-r1:
 * Log file: /var/log/portage/build/app-crypt/argon2-20190702-r1:20240813-224742.log

 * Package:    app-crypt/argon2-20190702-r1:0/1
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail],[e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox test userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 3676 KiB (3.5 MiB)
 * Final size of installed tree:   592 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: pkg-config files with mismatched Version found!
 * At least /usr/lib64/pkgconfig/libargon2.pc's Version field does not match 20190702
 * Please check all .pc files installed by this package.

 * Messages for package app-admin/pwgen-2.08-r2:
 * Log file: /var/log/portage/build/app-admin/pwgen-2.08-r2:20240813-224734.log

 * Package:    app-admin/pwgen-2.08-r2:0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail],[e-mail],[e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying pwgen-2.08-c2x.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 496 KiB
 * Final size of installed tree:   44 KiB
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/bin/pwgen

 * Messages for package app-portage/cpuid2cpuflags-14:
 * Log file: /var/log/portage/build/app-portage/cpuid2cpuflags-14:20240813-224758.log

 * Package:    app-portage/cpuid2cpuflags-14:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 824 KiB
 * Final size of installed tree:   20 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package app-shells/quoter-4.2:
 * Log file: /var/log/portage/build/app-shells/quoter-4.2:20240813-224802.log

 * Package:    app-shells/quoter-4.2:0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * Upstream:   [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 76 KiB
 * Final size of installed tree:  28 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package app-crypt/libmd-1.1.0:
 * Log file: /var/log/portage/build/app-crypt/libmd-1.1.0:20240813-224742.log

 * Package:    app-crypt/libmd-1.1.0:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox test userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * abi_x86_32.x86: running multilib-minimal_abi_src_configure
 * abi_x86_64.amd64: running multilib-minimal_abi_src_configure
 * abi_x86_32.x86: running multilib-minimal_abi_src_compile
 * abi_x86_64.amd64: running multilib-minimal_abi_src_compile
 * abi_x86_32.x86: running multilib-minimal_abi_src_test
 * abi_x86_64.amd64: running multilib-minimal_abi_src_test
 * abi_x86_32.x86: running multilib-minimal_abi_src_install
 * abi_x86_64.amd64: running multilib-minimal_abi_src_install
 * Final size of build directory: 5520 KiB (5.3 MiB)
 * Final size of installed tree:   384 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/lib/libmd.so.0.1.0
 * /usr/lib64/libmd.so.0.1.0
 * QA Notice: Package triggers severe warnings which indicate that it
 *            may exhibit random runtime failures.
 * /var/tmp/portage/app-crypt/libmd-1.1.0/work/libmd-1.1.0/src/sha1.c:135:25: warning: 'SHA1Transform.localalias' reading 64 bytes from a region of size 1 [-Wstringop-overread]
 * Please do not file a Gentoo bug and instead report the above QA
 * issues directly to the upstream developers of this software.
 * Homepage: https://www.hadrons.org/software/libmd/

 * Messages for package app-arch/unrar-7.0.9:
 * Log file: /var/log/portage/build/app-arch/unrar-7.0.9:20240813-224735.log

 * Package:    app-arch/unrar-7.0.9:0/7
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying unrar-6.2.6-honor-flags.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 14664 KiB (14.3 MiB)
 * Final size of installed tree:   1836 KiB ( 1.7 MiB)
 * CMP: =app-arch/unrar-7.0.9 with app-arch/unrar-7.0.9/image
 * ------> ABI(nodebug)
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package app-text/fzy-1.0-r1:
 * Log file: /var/log/portage/build/app-text/fzy-1.0-r1:20240813-224805.log

 * Package:    app-text/fzy-1.0-r1:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying 1.0-cflags.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Skipping make test/check due to ebuild restriction.
 * Your configuration for app-text/fzy-1.0-r1 has been saved in 
 * "/etc/portage/savedconfig/app-text/fzy-1.0-r1" for your editing pleasure.
 * You can edit these files by hand and remerge this package with
 * USE=savedconfig to customise the configuration.
 * You can rename this file/directory to one of the following for
 * its configuration to apply to multiple versions:
 * ${PORTAGE_CONFIGROOT}/etc/portage/savedconfig/
 * [${CTARGET}|${CHOST}|""]/${CATEGORY}/[${PF}|${P}|${PN}]
 * Final size of build directory: 532 KiB
 * Final size of installed tree:   80 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package app-misc/scrub-2.6.1-r2:
 * Log file: /var/log/portage/build/app-misc/scrub-2.6.1-r2:20240813-224745.log

 * Package:    app-misc/scrub-2.6.1-r2:0
 * Repository: gentoo
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox test userpriv usersandbox
 * Applying scrub-2.6.1-implicit-function-declaration-test.patch ...
 * Applying scrub-2.6.1-bashism-tests.patch ...
 * Applying scrub-2.6.1-tests-block-size.patch ...
 * Applying scrub-2.6.1-ub-fixes.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 3376 KiB (3.2 MiB)
 * Final size of installed tree:   148 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package app-text/manpager-1:
 * Log file: /var/log/portage/build/app-text/manpager-1:20240813-224807.log

 * Package:    app-text/manpager-1:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 80 KiB
 * Final size of installed tree:  84 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package app-text/scdoc-1.11.3:
 * Log file: /var/log/portage/build/app-text/scdoc-1.11.3:20240813-224811.log

 * Package:    app-text/scdoc-1.11.3:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 340 KiB
 * Final size of installed tree:   48 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/bin/scdoc

 * Messages for package app-text/t1utils-1.42:
 * Log file: /var/log/portage/build/app-text/t1utils-1.42:20240813-224812.log

 * Package:    app-text/t1utils-1.42:0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 1620 KiB (1.5 MiB)
 * Final size of installed tree:   388 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package app-arch/ncompress-5.0-r1:
 * Log file: /var/log/portage/build/app-arch/ncompress-5.0-r1:20240813-224735.log

 * Package:    app-arch/ncompress-5.0-r1:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 196 KiB
 * Final size of installed tree:   72 KiB
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package app-text/tree-2.1.1-r1:
 * Log file: /var/log/portage/build/app-text/tree-2.1.1-r1:20240813-224813.log

 * Package:    app-text/tree-2.1.1-r1:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 760 KiB
 * Final size of installed tree:  156 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/bin/tree

 * Messages for package app-text/libpaper-2.1.3:
 * Log file: /var/log/portage/build/app-text/libpaper-2.1.3:20240813-224807.log

 * Package:    app-text/libpaper-2.1.3:0/2
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Clang 16 testing: Found possible issues in configure (clang.diff)!
 * Clang 16 testing: Please check /var/tmp/clang/app-text/libpaper-2.1.3/clang.diff
 * Final size of build directory: 10924 KiB (10.6 MiB)
 * Final size of installed tree:    120 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/lib64/libpaper.so.2.1.3

 * Messages for package dev-build/pmake-1.111.3.3-r1:
 * Log file: /var/log/portage/build/dev-build/pmake-1.111.3.3-r1:20240813-224834.log

 * Package:    dev-build/pmake-1.111.3.3-r1:0
 * Repository: gentoo
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found sources for kernel version:
 *     6.6.45
 * Applying patches from /var/tmp/portage/dev-build/pmake-1.111.3.3-r1/work/debian/patches ...
 *   100_mk.diff ...
 *   110_mkdep.diff ...
 *   120_fixes.diff ...
 *   130_maxpathlen.diff ...
 *   140_multiarch.diff ...
 *   150_mktemp.diff ...
 * Applying pmake-1.98-skipdots.patch ...
 * Applying pmake-1.111.1-ldflags.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 2828 KiB (2.7 MiB)
 * Final size of installed tree:   528 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Package triggers severe warnings which indicate that it
 *            may exhibit random runtime failures.
 * main.c:603:25: warning: ‘__builtin_strncpy’ output may be truncated copying 4096 bytes from a string of length 4096 [-Wstringop-truncation]
 * Please do not file a Gentoo bug and instead report the above QA
 * issues directly to the upstream developers of this software.
 * Homepage: http://www.netbsd.org/

 * Messages for package dev-build/bmake-20240711:
 * Log file: /var/log/portage/build/dev-build/bmake-20240711:20240813-224823.log

 * Package:    dev-build/bmake-20240711:0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying bmake-20210206-tests.patch ...
 * Applying bmake-20210314-mk-fixes.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 8692 KiB (8.4 MiB)
 * Final size of installed tree:   816 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/bin/bmake

 * Messages for package dev-build/samurai-1.2-r3:
 * Log file: /var/log/portage/build/dev-build/samurai-1.2-r3:20240813-224843.log

 * Package:    dev-build/samurai-1.2-r3:0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying samurai-1.2-null_pointer_fix.patch ...
 * Applying samurai-1.2-phony_targets_fix.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 700 KiB
 * Final size of installed tree:  104 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/bin/samu

 * Messages for package dev-java/byaccj-1.15-r3:
 * Log file: /var/log/portage/build/dev-java/byaccj-1.15-r3:20240813-224851.log

 * Package:    dev-java/byaccj-1.15-r3:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying byaccj-1.15-implicit-function-declaration.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 960 KiB
 * Final size of installed tree:  136 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/bin/byaccj

 * Messages for package dev-db/lmdb-0.9.33:
 * Log file: /var/log/portage/build/dev-db/lmdb-0.9.33:20240813-224846.log

 * Package:    dev-db/lmdb-0.9.33:0/0.9.33
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Will copy sources from /var/tmp/portage/dev-db/lmdb-0.9.33/work/openldap-LMDB_0.9.33/libraries/liblmdb
 * abi_x86_32.x86: copying to /var/tmp/portage/dev-db/lmdb-0.9.33/work/openldap-LMDB_0.9.33/libraries/liblmdb-abi_x86_32.x86
 * abi_x86_64.amd64: copying to /var/tmp/portage/dev-db/lmdb-0.9.33/work/openldap-LMDB_0.9.33/libraries/liblmdb-abi_x86_64.amd64
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * abi_x86_32.x86: running multilib-minimal_abi_src_configure
 * abi_x86_64.amd64: running multilib-minimal_abi_src_configure
 * abi_x86_32.x86: running multilib-minimal_abi_src_compile
 * abi_x86_64.amd64: running multilib-minimal_abi_src_compile
 * abi_x86_32.x86: running multilib-minimal_abi_src_install
 * abi_x86_64.amd64: running multilib-minimal_abi_src_install
 * Final size of build directory: 6972 KiB (6.8 MiB)
 * Final size of installed tree:   692 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/lib/liblmdb.so.0
 * /usr/lib64/liblmdb.so.0
 * QA Notice: Package triggers severe warnings which indicate that it
 *            may exhibit random runtime failures.
 * mdb.c:5247:20: warning: ‘env’ may be used uninitialized [-Wmaybe-uninitialized]
 * Please do not file a Gentoo bug and instead report the above QA
 * issues directly to the upstream developers of this software.
 * Homepage: https://symas.com/lmdb/technical/

 * Messages for package dev-lang/duktape-2.7.0-r3:
 * Log file: /var/log/portage/build/dev-lang/duktape-2.7.0-r3:20240813-224859.log

 * Package:    dev-lang/duktape-2.7.0-r3:0/2.7.0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying duktape-2.7.0-respect-tc-env.patch ...
 * Applying duktape-2.7.0-underlinked-libm.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 22328 KiB (21.8 MiB)
 * Final size of installed tree:   1520 KiB ( 1.4 MiB)
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Package triggers severe warnings which indicate that it
 *            may exhibit random runtime failures.
 * duk_bi_buffer.c:1397:13: warning: ‘length’ may be used uninitialized [-Wmaybe-uninitialized]
 * duk_bi_buffer.c:1420:3: warning: ‘offset’ may be used uninitialized [-Wmaybe-uninitialized]
 * duk_bi_buffer.c:1397:13: warning: ‘length’ may be used uninitialized [-Wmaybe-uninitialized]
 * duk_bi_buffer.c:1420:3: warning: ‘offset’ may be used uninitialized [-Wmaybe-uninitialized]
 * duk_bi_buffer.c:1050:13: warning: ‘length’ may be used uninitialized [-Wmaybe-uninitialized]
 * duk_bi_buffer.c:1075:38: warning: ‘offset’ may be used uninitialized [-Wmaybe-uninitialized]
 * duk_bi_buffer.c:1050:13: warning: ‘length’ may be used uninitialized [-Wmaybe-uninitialized]
 * duk_bi_buffer.c:1075:38: warning: ‘offset’ may be used uninitialized [-Wmaybe-uninitialized]
 * duk_js_compiler.c:5933:5: warning: ‘label_catch_depth’ may be used uninitialized [-Wmaybe-uninitialized]
 * duk_js_compiler.c:5933:59: warning: ‘label_is_closest’ may be used uninitialized [-Wmaybe-uninitialized]
 * duk_js_compiler.c:1613:2: warning: ‘label_id’ may be used uninitialized [-Wmaybe-uninitialized]
 * duk_js_compiler.c:5943:3: warning: ‘label_pc’ may be used uninitialized [-Wmaybe-uninitialized]
 * duk_js_compiler.c:5933:5: warning: ‘label_catch_depth’ may be used uninitialized [-Wmaybe-uninitialized]
 * duk_js_compiler.c:5933:59: warning: ‘label_is_closest’ may be used uninitialized [-Wmaybe-uninitialized]
 * duk_js_compiler.c:1613:2: warning: ‘label_id’ may be used uninitialized [-Wmaybe-uninitialized]
 * duk_js_compiler.c:5943:3: warning: ‘label_pc’ may be used uninitialized [-Wmaybe-uninitialized]
 * Please do not file a Gentoo bug and instead report the above QA
 * issues directly to the upstream developers of this software.
 * Homepage: https://duktape.org

 * Messages for package dev-build/b2-5.2.1:
 * Log file: /var/log/portage/build/dev-build/b2-5.2.1:20240813-224822.log

 * Package:    dev-build/b2-5.2.1:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying b2-4.9.2-disable_python_rpath.patch ...
 * Applying b2-4.9.2-darwin-gentoo-toolchain.patch ...
 * Applying b2-4.9.2-add-none-feature-options.patch ...
 * Applying b2-4.9.2-no-implicit-march-flags.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * /usr/bin/bash ./build.sh cxx --cxx=x86_64-pc-linux-gnu-g++ --cxxflags=-pthread -O3 -march=native -mtls-dialect=gnu2 -flto=jobserver -fno-semantic-interposition -pipe -fcf-protection=none -fdiagnostics-color=always -fdiagnostics-urls=never -frecord-gcc-switches -Wa,-O2 -Wa,-mtune=znver2  -Wstrict-aliasing -Wfree-nonheap-object -Werror=lto-type-mismatch -Werror=strict-aliasing -Werror=odr  -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs -flto=jobserver -fuse-ld=mold -Wl,--defsym=__gentoo_check_ldflags__=0 -d+2 --without-python
 * Skipping make test/check due to ebuild restriction.
 * Final size of build directory: 8748 KiB (8.5 MiB)
 * Final size of installed tree:  3148 KiB (3.0 MiB)
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package dev-lang/luajit-2.1.1716656478:
 * Log file: /var/log/portage/build/dev-lang/luajit-2.1.1716656478:20240813-224911.log

 * Package:    dev-lang/luajit-2.1.1716656478:2/2.1.1716656478
 * Repository: gentoo
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 11732 KiB (11.4 MiB)
 * Final size of installed tree:   1468 KiB ( 1.4 MiB)
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/bin/luajit-2.1.1716656478
 * /usr/lib64/libluajit-5.1.so.2.1.1716656478
 * QA Notice: Files built without respecting LDFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/lib64/libluajit-5.1.so.2.1.1716656478

 * Messages for package dev-libs/liblinear-246:
 * Log file: /var/log/portage/build/dev-libs/liblinear-246:20240813-224930.log

 * Package:    dev-libs/liblinear-246:0/5
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox
 * SED: some expressions in the following did not cause any changes
 *     sed -i -e '/install_name/s:liblinear.so.$(SHVER):'"${EPREFIX}"'/usr/lib/liblinear.$(SHVER).dylib:' -e '/LDFLAGS/s:liblinear.so.$(SHVER):liblinear'"$(get_libname '$(SHVER)')"':' Makefile || die
 * no-op: -e /LDFLAGS/s:liblinear.so.$(SHVER):liblinear.so.$(SHVER):
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 3680 KiB (3.5 MiB)
 * Final size of installed tree:  1420 KiB (1.3 MiB)
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Package triggers severe warnings which indicate that it
 *            may exhibit random runtime failures.
 * /usr/include/bits/stdio2.h:118:23: warning: ‘best_C’ may be used uninitialized [-Wmaybe-uninitialized]
 * /usr/include/bits/stdio2.h:118:23: warning: ‘best_score’ may be used uninitialized [-Wmaybe-uninitialized]
 * Please do not file a Gentoo bug and instead report the above QA
 * issues directly to the upstream developers of this software.
 * Homepage: https://www.csie.ntu.edu.tw/~cjlin/liblinear/ https://github.com/cjlin1/liblinear

 * Messages for package dev-libs/libutf8proc-2.9.0:
 * Log file: /var/log/portage/build/dev-libs/libutf8proc-2.9.0:20240813-224941.log

 * Package:    dev-libs/libutf8proc-2.9.0:0/2.9.0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Skipping make test/check due to ebuild restriction.
 * Final size of build directory: 3916 KiB (3.8 MiB)
 * Final size of installed tree:   388 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/lib64/libutf8proc.so.3.0.0

 * Messages for package dev-libs/libaio-0.3.113-r1:
 * Log file: /var/log/portage/build/dev-libs/libaio-0.3.113-r1:20240813-224927.log

 * Package:    dev-libs/libaio-0.3.113-r1:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux test
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox
 * Applying libaio-0.3.112-cppflags.patch ...
 * Applying libaio-0.3.113-respect-LDFLAGS.patch ...
 * Applying libaio-0.3.113-32-bit-tests.patch ...
 * SED: some expressions in the following did not cause any changes
 *     sed -i "${sed_args[@]}" src/Makefile harness/Makefile Makefile || die;
 * no-op: -e /^prefix=/s:/usr:/usr:
 * Will copy sources from /var/tmp/portage/dev-libs/libaio-0.3.113-r1/work/libaio-0.3.113
 * abi_x86_32.x86: copying to /var/tmp/portage/dev-libs/libaio-0.3.113-r1/work/libaio-0.3.113-abi_x86_32.x86
 * abi_x86_64.amd64: copying to /var/tmp/portage/dev-libs/libaio-0.3.113-r1/work/libaio-0.3.113-abi_x86_64.amd64
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * abi_x86_32.x86: running multilib-minimal_abi_src_configure
 * abi_x86_64.amd64: running multilib-minimal_abi_src_configure
 * abi_x86_32.x86: running multilib-minimal_abi_src_compile
 * abi_x86_64.amd64: running multilib-minimal_abi_src_compile
 * abi_x86_32.x86: running multilib-minimal_abi_src_test
 * abi_x86_64.amd64: running multilib-minimal_abi_src_test
 * abi_x86_32.x86: running multilib-minimal_abi_src_install
 * abi_x86_64.amd64: running multilib-minimal_abi_src_install
 * Final size of build directory: 35608 KiB (34.7 MiB)
 * Final size of installed tree:    800 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package dev-libs/mpdecimal-4.0.0:
 * Log file: /var/log/portage/build/dev-libs/mpdecimal-4.0.0:20240813-225216.log

 * Package:    dev-libs/mpdecimal-4.0.0:4
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Skipping make test/check due to ebuild restriction.
 * Final size of build directory: 3736 KiB (3.6 MiB)
 * Final size of installed tree:   620 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/lib64/libmpdec.so.4.0.0

 * Messages for package dev-lang/go-1.22.6:
 * Log file: /var/log/portage/build/dev-lang/go-1.22.6:20240813-224902.log

 * Package:    dev-lang/go-1.22.6:0/1.22.6
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 cpu_flags_x86_sse2 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying go-never-download-newer-toolchains.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 258876 KiB (252.8 MiB)
 * Final size of installed tree:  234440 KiB (228.9 MiB)
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package dev-libs/tree-sitter-0.22.6:
 * Log file: /var/log/portage/build/dev-libs/tree-sitter-0.22.6:20240813-225239.log

 * Package:    dev-libs/tree-sitter-0.22.6:0/0.22.6
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail],[e-mail],[e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox
 * Applying tree-sitter-0.22.2-no-static.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Skipping make test/check due to ebuild restriction.
 * Final size of build directory: 14056 KiB (13.7 MiB)
 * Final size of installed tree:   1172 KiB ( 1.1 MiB)
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package dev-libs/oniguruma-6.9.9:
 * Log file: /var/log/portage/build/dev-libs/oniguruma-6.9.9:20240813-225230.log

 * Package:    dev-libs/oniguruma-6.9.9:0/5
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * abi_x86_32.x86: running multilib-minimal_abi_src_configure
 * abi_x86_64.amd64: running multilib-minimal_abi_src_configure
 * abi_x86_32.x86: running multilib-minimal_abi_src_compile
 * abi_x86_64.amd64: running multilib-minimal_abi_src_compile
 * abi_x86_32.x86: running multilib-minimal_abi_src_install
 * abi_x86_64.amd64: running multilib-minimal_abi_src_install
 * Final size of build directory: 13144 KiB (12.8 MiB)
 * Final size of installed tree:   1960 KiB ( 1.9 MiB)
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/lib/libonig.so.5.4.0
 * /usr/lib64/libonig.so.5.4.0

 * Messages for package dev-libs/tree-sitter-c-0.21.4:
 * Log file: /var/log/portage/build/dev-libs/tree-sitter-c-0.21.4:20240813-225249.log

 * Package:    dev-libs/tree-sitter-c-0.21.4:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux python_targets_python3_10 python_targets_python3_11 python_targets_python3_12 python_targets_python3_13
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Skipping make test/check due to ebuild restriction.
 * Final size of build directory: 6588 KiB (6.4 MiB)
 * Final size of installed tree:   668 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package dev-libs/lzo-2.10:
 * Log file: /var/log/portage/build/dev-libs/lzo-2.10:20240813-225211.log

 * Package:    dev-libs/lzo-2.10:2
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox test userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * abi_x86_32.x86: running multilib-minimal_abi_src_configure
 * abi_x86_64.amd64: running multilib-minimal_abi_src_configure
 * abi_x86_32.x86: running multilib-minimal_abi_src_compile
 * abi_x86_64.amd64: running multilib-minimal_abi_src_compile
 * abi_x86_32.x86: running multilib-minimal_abi_src_test
 * abi_x86_64.amd64: running multilib-minimal_abi_src_test
 * abi_x86_32.x86: running multilib-minimal_abi_src_install
 * abi_x86_64.amd64: running multilib-minimal_abi_src_install
 * Final size of build directory: 11224 KiB (10.9 MiB)
 * Final size of installed tree:    796 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/lib/liblzo2.so.2.0.0
 * /usr/lib64/liblzo2.so.2.0.0
 * QA Notice: Package triggers severe warnings which indicate that it
 *            may exhibit random runtime failures.
 * /var/tmp/portage/dev-libs/lzo-2.10/work/lzo-2.10/examples/portab.h:133:25: warning: 'p_7' may be used uninitialized [-Wmaybe-uninitialized]
 * /var/tmp/portage/dev-libs/lzo-2.10/work/lzo-2.10/lzotest/lzotest.c:357:35: warning: '_4' may be used uninitialized [-Wmaybe-uninitialized]
 * /var/tmp/portage/dev-libs/lzo-2.10/work/lzo-2.10/examples/portab.h:133:25: warning: 'p_7' may be used uninitialized [-Wmaybe-uninitialized]
 * /var/tmp/portage/dev-libs/lzo-2.10/work/lzo-2.10/lzotest/lzotest.c:357:35: warning: '_4' may be used uninitialized [-Wmaybe-uninitialized]
 * Please do not file a Gentoo bug and instead report the above QA
 * issues directly to the upstream developers of this software.
 * Homepage: https://www.oberhumer.com/opensource/lzo/

 * Messages for package dev-libs/tree-sitter-cpp-0.22.2:
 * Log file: /var/log/portage/build/dev-libs/tree-sitter-cpp-0.22.2:20240813-225255.log

 * Package:    dev-libs/tree-sitter-cpp-0.22.2:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux python_targets_python3_10 python_targets_python3_11 python_targets_python3_12 python_targets_python3_13
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Skipping make test/check due to ebuild restriction.
 * Final size of build directory: 24788 KiB (24.2 MiB)
 * Final size of installed tree:   3244 KiB ( 3.1 MiB)
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package dev-libs/xxhash-0.8.2:
 * Log file: /var/log/portage/build/dev-libs/xxhash-0.8.2:20240813-225258.log

 * Package:    dev-libs/xxhash-0.8.2:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * Upstream:   https://github.com/Cyan4973/xxHash/issues
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Will copy sources from /var/tmp/portage/dev-libs/xxhash-0.8.2/work/xxHash-0.8.2
 * abi_x86_32.x86: copying to /var/tmp/portage/dev-libs/xxhash-0.8.2/work/xxHash-0.8.2-abi_x86_32.x86
 * abi_x86_64.amd64: copying to /var/tmp/portage/dev-libs/xxhash-0.8.2/work/xxHash-0.8.2-abi_x86_64.amd64
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * abi_x86_32.x86: running multilib-minimal_abi_src_configure
 * abi_x86_64.amd64: running multilib-minimal_abi_src_configure
 * abi_x86_32.x86: running multilib-minimal_abi_src_compile
 * abi_x86_64.amd64: running multilib-minimal_abi_src_compile
 * abi_x86_32.x86: running multilib-minimal_abi_src_install
 * abi_x86_64.amd64: running multilib-minimal_abi_src_install
 * Final size of build directory: 18048 KiB (17.6 MiB)
 * Final size of installed tree:    536 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package dev-util/libtree-3.1.1:
 * Log file: /var/log/portage/build/dev-util/libtree-3.1.1:20240813-225311.log

 * Package:    dev-util/libtree-3.1.1:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying libtree-3.1.1-modern-c.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 344 KiB
 * Final size of installed tree:   44 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/bin/libtree

 * Messages for package dev-util/gperf-3.1-r2:
 * Log file: /var/log/portage/build/dev-util/gperf-3.1-r2:20240813-225308.log

 * Package:    dev-util/gperf-3.1-r2:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox test userpriv usersandbox
 * Applying gperf-3.1-strncmp-decl-mismatch.patch ...
 * Applying gperf-3.1-clang-16-wregister.patch ...
 * Applying gperf-3.1-parallel-tests.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 4888 KiB (4.7 MiB)
 * Final size of installed tree:   548 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package dev-util/unifdef-2.12-r1:
 * Log file: /var/log/portage/build/dev-util/unifdef-2.12-r1:20240813-225321.log

 * Package:    dev-util/unifdef-2.12-r1:0
 * Repository: gentoo
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying unifdef-2.12-tests.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 2060 KiB (2.0 MiB)
 * Final size of installed tree:   352 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package cross-arm-none-eabi/newlib-4.4.0.20231231:
 * Log file: /var/log/portage/build/cross-arm-none-eabi/newlib-4.4.0.20231231:20240813-224818.log

 * Package:    cross-arm-none-eabi/newlib-4.4.0.20231231:0
 * Repository: crossdev
 * Maintainer: [e-mail] [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux nls unicode
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying newlib-3.3.0-no-nano-cxx.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Missing dejagnu tests?
 * Final size of build directory: 1015656 KiB (991.8 MiB)
 * Final size of installed tree:   301780 KiB (294.7 MiB)
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package games-util/catcodec-1.0.5:
 * Log file: /var/log/portage/build/games-util/catcodec-1.0.5:20240813-225325.log

 * Package:    games-util/catcodec-1.0.5:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 2240 KiB (2.1 MiB)
 * Final size of installed tree:   720 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package dev-util/re2c-3.1:
 * Log file: /var/log/portage/build/dev-util/re2c-3.1:20240813-225318.log

 * Package:    dev-util/re2c-3.1:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Skipping make test/check due to ebuild restriction.
 * Final size of build directory: 64264 KiB (62.7 MiB)
 * Final size of installed tree:   4748 KiB ( 4.6 MiB)
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package media-libs/giflib-5.2.2:
 * Log file: /var/log/portage/build/media-libs/giflib-5.2.2:20240813-225329.log

 * Package:    media-libs/giflib-5.2.2:0/7
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox
 * Applying giflib-5.2.1-fix-missing-quantize-API-symbols.patch ...
 * Applying giflib-5.2.2-fortify.patch ...
 * Applying giflib-5.2.2-verbose-tests.patch ...
 * Will copy sources from /var/tmp/portage/media-libs/giflib-5.2.2/work/giflib-5.2.2
 * abi_x86_32.x86: copying to /var/tmp/portage/media-libs/giflib-5.2.2/work/giflib-5.2.2-abi_x86_32.x86
 * abi_x86_64.amd64: copying to /var/tmp/portage/media-libs/giflib-5.2.2/work/giflib-5.2.2-abi_x86_64.amd64
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * abi_x86_32.x86: running multilib-minimal_abi_src_configure
 * abi_x86_64.amd64: running multilib-minimal_abi_src_configure
 * abi_x86_32.x86: running multilib-minimal_abi_src_compile
 * abi_x86_64.amd64: running multilib-minimal_abi_src_compile
 * abi_x86_32.x86: running multilib-minimal_abi_src_install
 * abi_x86_64.amd64: running multilib-minimal_abi_src_install
 * Final size of build directory: 20960 KiB (20.4 MiB)
 * Final size of installed tree:   2884 KiB ( 2.8 MiB)
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Package triggers severe warnings which indicate that it
 *            may exhibit random runtime failures.
 * gifsponge.c:84:17: warning: ‘ErrorCode’ may be used uninitialized [-Wmaybe-uninitialized]
 * /usr/include/bits/stdio2.h:118:10: warning: ‘gcb.DisposalMode’ may be used uninitialized [-Wmaybe-uninitialized]
 * giftool.c:520:68: warning: ‘MEM <unsigned char> [(struct GraphicsControlBlock *)&gcb + 4B]’ may be used uninitialized [-Wmaybe-uninitialized]
 * /usr/include/bits/stdio2.h:118:10: warning: ‘gcb.TransparentColor’ may be used uninitialized [-Wmaybe-uninitialized]
 * /usr/include/bits/stdio2.h:118:10: warning: ‘gcb.DelayTime’ may be used uninitialized [-Wmaybe-uninitialized]
 * giftool.c:644:17: warning: ‘ErrorCode’ may be used uninitialized [-Wmaybe-uninitialized]
 * gifbuild.c:130:17: warning: ‘ErrorCode’ may be used uninitialized [-Wmaybe-uninitialized]
 * gif2rgb.c:525:25: warning: ‘Error’ may be used uninitialized [-Wmaybe-uninitialized]
 * gifsponge.c:84:17: warning: ‘ErrorCode’ may be used uninitialized [-Wmaybe-uninitialized]
 * /usr/include/bits/stdio2.h:118:10: warning: ‘gcb.DisposalMode’ may be used uninitialized [-Wmaybe-uninitialized]
 * giftool.c:520:68: warning: ���MEM <unsigned char> [(struct GraphicsControlBlock *)&gcb + 4B]’ may be used uninitialized [-Wmaybe-uninitialized]
 * /usr/include/bits/stdio2.h:118:10: warning: ‘gcb.TransparentColor’ may be used uninitialized [-Wmaybe-uninitialized]
 * /usr/include/bits/stdio2.h:118:10: warning: ‘gcb.DelayTime’ may be used uninitialized [-Wmaybe-uninitialized]
 * giftool.c:644:17: warning: ‘ErrorCode’ may be used uninitialized [-Wmaybe-uninitialized]
 * gifbuild.c:130:17: warning: ‘ErrorCode’ may be used uninitialized [-Wmaybe-uninitialized]
 * gif2rgb.c:525:25: warning: ‘Error’ may be used uninitialized [-Wmaybe-uninitialized]
 * Please do not file a Gentoo bug and instead report the above QA
 * issues directly to the upstream developers of this software.
 * Homepage: https://sourceforge.net/projects/giflib/

 * Messages for package dev-util/cppunit-1.15.1-r3:
 * Log file: /var/log/portage/build/dev-util/cppunit-1.15.1-r3:20240813-225303.log

 * Package:    dev-util/cppunit-1.15.1-r3:0/1.15
 * Repository: gentoo
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * abi_x86_32.x86: running multilib-minimal_abi_src_configure
 * abi_x86_64.amd64: running multilib-minimal_abi_src_configure
 * abi_x86_32.x86: running multilib-minimal_abi_src_compile
 * abi_x86_64.amd64: running multilib-minimal_abi_src_compile
 * abi_x86_32.x86: running multilib-minimal_abi_src_install
 * abi_x86_64.amd64: running multilib-minimal_abi_src_install
 * Final size of build directory: 15680 KiB (15.3 MiB)
 * Final size of installed tree:   1576 KiB ( 1.5 MiB)
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/lib/libcppunit-1.15.so.1.0.0
 * /usr/lib64/libcppunit-1.15.so.1.0.0

 * Messages for package media-libs/libdvbpsi-1.3.3:
 * Log file: /var/log/portage/build/media-libs/libdvbpsi-1.3.3:20240813-225336.log

 * Package:    media-libs/libdvbpsi-1.3.3:0/10
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * SED: some expressions in the following did not cause any changes
 *     sed -e '/CFLAGS/s:-O2::' -e '/CFLAGS/s:-O6::' -e '/CFLAGS/s:-Werror::' -i configure || die;
 * no-op: -e /CFLAGS/s:-O6::
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 7384 KiB (7.2 MiB)
 * Final size of installed tree:   888 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/lib64/libdvbpsi.so.10.0.0

 * Messages for package media-libs/libfreeaptx-0.1.1-r1:
 * Log file: /var/log/portage/build/media-libs/libfreeaptx-0.1.1-r1:20240813-225352.log

 * Package:    media-libs/libfreeaptx-0.1.1-r1:0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 cpu_flags_x86_avx2 elibc_glibc kernel_linux
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox
 * Applying libfreeaptx-0.1.1-fix-version.patch ...
 * Will copy sources from /var/tmp/portage/media-libs/libfreeaptx-0.1.1-r1/work/libfreeaptx-0.1.1
 * abi_x86_32.x86: copying to /var/tmp/portage/media-libs/libfreeaptx-0.1.1-r1/work/libfreeaptx-0.1.1-abi_x86_32.x86
 * abi_x86_64.amd64: copying to /var/tmp/portage/media-libs/libfreeaptx-0.1.1-r1/work/libfreeaptx-0.1.1-abi_x86_64.amd64
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * abi_x86_32.x86: running multilib-minimal_abi_src_configure
 * abi_x86_64.amd64: running multilib-minimal_abi_src_configure
 * abi_x86_32.x86: running multilib-minimal_abi_src_compile
 * abi_x86_64.amd64: running multilib-minimal_abi_src_compile
 * abi_x86_32.x86: running multilib-minimal_abi_src_install
 * abi_x86_64.amd64: running multilib-minimal_abi_src_install
 * Final size of build directory: 1184 KiB (1.1 MiB)
 * Final size of installed tree:   444 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package net-libs/http-parser-2.9.4-r2:
 * Log file: /var/log/portage/build/net-libs/http-parser-2.9.4-r2:20240813-225400.log

 * Package:    net-libs/http-parser-2.9.4-r2:0/2.9.4
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying http-parser-2.9.4-non-x86-test.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 408 KiB
 * Final size of installed tree:   76 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/lib64/libhttp_parser.so.2.9.4

 * Messages for package media-libs/libdvdcss-1.4.3:
 * Log file: /var/log/portage/build/media-libs/libdvdcss-1.4.3:20240813-225349.log

 * Package:    media-libs/libdvdcss-1.4.3:1.2
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * abi_x86_32.x86: running multilib-minimal_abi_src_configure
 * abi_x86_64.amd64: running multilib-minimal_abi_src_configure
 * abi_x86_32.x86: running multilib-minimal_abi_src_compile
 * abi_x86_64.amd64: running multilib-minimal_abi_src_compile
 * abi_x86_32.x86: running multilib-minimal_abi_src_install
 * abi_x86_64.amd64: running multilib-minimal_abi_src_install
 * Final size of build directory: 4256 KiB (4.1 MiB)
 * Final size of installed tree:   308 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/lib/libdvdcss.so.2.2.0
 * /usr/lib64/libdvdcss.so.2.2.0

 * Messages for package media-libs/libogg-1.3.5-r1:
 * Log file: /var/log/portage/build/media-libs/libogg-1.3.5-r1:20240813-225355.log

 * Package:    media-libs/libogg-1.3.5-r1:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox test userpriv usersandbox
 * Applying libogg-1.3.4-libdir-m4.patch ...
 * Applying libogg-1.3.5-macro-wstrict-prototypes.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * abi_x86_32.x86: running multilib-minimal_abi_src_configure
 * abi_x86_64.amd64: running multilib-minimal_abi_src_configure
 * abi_x86_32.x86: running multilib-minimal_abi_src_compile
 * abi_x86_64.amd64: running multilib-minimal_abi_src_compile
 * abi_x86_32.x86: running multilib-minimal_abi_src_test
 * abi_x86_64.amd64: running multilib-minimal_abi_src_test
 * abi_x86_32.x86: running multilib-minimal_abi_src_install
 * abi_x86_64.amd64: running multilib-minimal_abi_src_install
 * Found -ffast-math in build.log!
 * Final size of build directory: 5176 KiB (5.0 MiB)
 * Final size of installed tree:   716 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/lib/libogg.so.0.8.5
 * /usr/lib64/libogg.so.0.8.5

 * Messages for package sys-apps/hdparm-9.65-r2:
 * Log file: /var/log/portage/build/sys-apps/hdparm-9.65-r2:20240813-225411.log

 * Package:    sys-apps/hdparm-9.65-r2:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying hdparm-9.60-build.patch ...
 * Applying hdparm-9.65-graceful-lfs.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 1380 KiB (1.3 MiB)
 * Final size of installed tree:   324 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package media-sound/gsm-1.0.22_p1:
 * Log file: /var/log/portage/build/media-sound/gsm-1.0.22_p1:20240813-225358.log

 * Package:    media-sound/gsm-1.0.22_p1:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_32 abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying gsm-1.0.12-memcpy.patch ...
 * Applying gsm-1.0.12-64bit.patch ...
 * Applying patches from /var/tmp/portage/media-sound/gsm-1.0.22_p1/work/debian/patches ...
 *   04_includes.patch ...
 *   05_compiler_warnings.patch ...
 *   06_fix_manpages.patch ...
 * Applying gsm-1.0.22-makefile.patch ...
 * SED: the following did not cause any changes
 *     sed -e 's/\$(GSM_INSTALL_LIB)\/libgsm.a    //g' -i Makefile || die;
 * no-op: -e s/\$(GSM_INSTALL_LIB)\/libgsm.a	//g
 * Will copy sources from /var/tmp/portage/media-sound/gsm-1.0.22_p1/work/gsm-1.0-pl22
 * abi_x86_32.x86: copying to /var/tmp/portage/media-sound/gsm-1.0.22_p1/work/gsm-1.0-pl22-abi_x86_32.x86
 * abi_x86_64.amd64: copying to /var/tmp/portage/media-sound/gsm-1.0.22_p1/work/gsm-1.0-pl22-abi_x86_64.amd64
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * abi_x86_32.x86: running multilib-minimal_abi_src_compile
 * abi_x86_64.amd64: running multilib-minimal_abi_src_compile
 * abi_x86_32.x86: running multilib-minimal_abi_src_install
 * abi_x86_64.amd64: running multilib-minimal_abi_src_install
 * Final size of build directory: 2624 KiB (2.5 MiB)
 * Final size of installed tree:   292 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/bin/toast
 * /usr/lib/libgsm.so.1.0.19
 * /usr/lib64/libgsm.so.1.0.19

 * Messages for package sys-apps/i2c-tools-4.3-r2:
 * Log file: /var/log/portage/build/sys-apps/i2c-tools-4.3-r2:20240813-225416.log

 * Package:    sys-apps/i2c-tools-4.3-r2:0
 * Repository: gentoo
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux python_targets_python3_10 python_targets_python3_11 python_targets_python3_12
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 952 KiB
 * Final size of installed tree:  412 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/lib64/libi2c.so.0.1.1
 * /usr/sbin/i2cdetect
 * /usr/sbin/eeprog
 * /usr/sbin/i2cdump
 * /usr/sbin/i2cset
 * /usr/sbin/i2cget
 * /usr/sbin/i2ctransfer

 * Messages for package sys-apps/install-xattr-0.8-r1:
 * Log file: /var/log/portage/build/sys-apps/install-xattr-0.8-r1:20240813-225419.log

 * Package:    sys-apps/install-xattr-0.8-r1:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug test userpriv usersandbox
 * Applying patches from /var/tmp/portage/sys-apps/install-xattr-0.8-r1/files/0.8 ...
 *   0001-install-xattr-avoid-accessing-empty-storage.patch ...
 *   0002-install-xattr-fix-small-memory-leak.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 180 KiB
 * Final size of installed tree:  116 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package net-misc/passt-2024.06.07:
 * Log file: /var/log/portage/build/net-misc/passt-2024.06.07:20240813-225408.log

 * Package:    net-misc/passt-2024.06.07:0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail],[e-mail]
 * Upstream:   https://passt.top/passt/bugs
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying Makefile-2024.03.20.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 2316 KiB (2.2 MiB)
 * Final size of installed tree:   936 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Package triggers severe warnings which indicate that it
 *            may exhibit random runtime failures.
 * tap.c:666:25: warning: ‘l2len’ may be used uninitialized [-Wmaybe-uninitialized]
 * Please do not file a Gentoo bug and instead report the above QA
 * issues directly to the upstream developers of this software.
 * Homepage: https://passt.top/

 * Messages for package sys-apps/man2html-1.6g-r2:
 * Log file: /var/log/portage/build/sys-apps/man2html-1.6g-r2:20240813-225421.log

 * Package:    sys-apps/man2html-1.6g-r2:0
 * Repository: gentoo
 * Maintainer: [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   compressdebug dedupdebug installsources network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox
 * Applying man-1.6f-man2html-compression-2.patch ...
 * Applying man-1.6-cross-compile.patch ...
 * Applying man-1.6g-compress.patch ...
 * Applying man-1.6g-clang-15-configure.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * ./configure -confdir=/etc +sgid +fhs +lang none
 * Final size of build directory: 2272 KiB (2.2 MiB)
 * Final size of installed tree:   336 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.

 * Messages for package sys-devel/qbe-1.2:
 * Log file: /var/log/portage/build/sys-devel/qbe-1.2:20240813-225424.log

 * Package:    sys-devel/qbe-1.2:0
 * Repository: gentoo
 * Maintainer: [e-mail] [e-mail]
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 3476 KiB (3.3 MiB)
 * Final size of installed tree:   380 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/bin/qbe

 * Messages for package sys-process/schedtool-1.3.0-r2:
 * Log file: /var/log/portage/build/sys-process/schedtool-1.3.0-r2:20240813-225432.log

 * Package:    sys-process/schedtool-1.3.0-r2:0
 * Repository: gentoo
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux
 * FEATURES:   network-sandbox preserve-libs sandbox userpriv usersandbox
 * Applying schedtool-1.3.0-c99.patch ...
 * Modern C testing: this build is using a /etc/portage/bashrc hook ()!
 * Modern C testing: see https://wiki.gentoo.org/wiki/Modern_C_porting for more info.
 * Final size of build directory: 192 KiB
 * Final size of installed tree:   76 KiB
 * The ebuild phase 'instprep' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.
 * The ebuild phase 'other' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
 * QA Notice: Files built without respecting CFLAGS have been detected
 *  Please include the following list of files in your report:
 * /usr/bin/schedtool

====================================
Error in portage.process.run_exitfuncs

  File "/usr/lib/python3.13/site-packages/portage/process.py", line 227, in run_exitfuncs
    func(*targs, **kargs)
    ~~~~^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.13/shutil.py", line 763, in rmtree
    _rmtree_safe_fd(stack, onexc)
    ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
  File "/usr/lib/python3.13/shutil.py", line 704, in _rmtree_safe_fd
    onexc(func, path, err)
    ~~~~~^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.13/shutil.py", line 665, in _rmtree_safe_fd
    orig_st = os.lstat(name, dir_fd=dirfd)
[Errno 2] No such file or directory: '/var/tmp/portage/._portage_reinstall_._75lho_q'
====================================

Exception ignored in atexit callback <function run_exitfuncs at 0x7f58e8d637e0>:
Traceback (most recent call last):
  File "/usr/lib/python3.13/site-packages/portage/process.py", line 235, in run_exitfuncs
    raise exc_info[0](exc_info[1]).with_traceback(exc_info[2])
  File "/usr/lib/python3.13/site-packages/portage/process.py", line 227, in run_exitfuncs
    func(*targs, **kargs)
  File "/usr/lib/python3.13/shutil.py", line 763, in rmtree
    _rmtree_safe_fd(stack, onexc)
  File "/usr/lib/python3.13/shutil.py", line 704, in _rmtree_safe_fd
    onexc(func, path, err)
  File "/usr/lib/python3.13/shutil.py", line 665, in _rmtree_safe_fd
    orig_st = os.lstat(name, dir_fd=dirfd)
FileNotFoundError: [Errno 2] No such file or directory: '/var/tmp/portage/._portage_reinstall_._75lho_q'