https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-libs/octetos-coreutils-0.17.0_alpha fails tests. Discovered on: amd64 (internal ref: guru_tinderbox) NOTE: This machine uses GCC-11: https://gcc.gnu.org/gcc-11/porting_to.html
Created attachment 742821 [details] build.log build log and emerge --info
Possible context of error(s): /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: v0.cc:(.text+0x13b): undefined reference to `CU_assertImplementation' /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: v0.cc:(.text+0x20f): undefined reference to `CU_assertImplementation' /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: v0.cc:(.text+0x29a): undefined reference to `CU_assertImplementation' /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: v0.cc:(.text+0x319): undefined reference to `CU_assertImplementation' /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: v0.cc:(.text.startup+0x23): undefined reference to `CU_add_suite' /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: v0.cc:(.text.startup+0x39): undefined reference to `CU_add_test' /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: v0.cc:(.text.startup+0x48): undefined reference to `CU_basic_set_mode' /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: v0.cc:(.text.startup+0x4d): undefined reference to `CU_basic_run_tests' /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: v0.cc:(.text.startup+0x52): undefined reference to `CU_cleanup_registry' /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: v0.cc:(.text.startup+0x5b): undefined reference to `CU_get_error' v0.cc:(.text+0xce): undefined reference to `CU_assertImplementation' v0.cc:(.text.startup+0x5): undefined reference to `CU_initialize_registry' collect2: error: ld returned 1 exit status
*** Bug 816105 has been marked as a duplicate of this bug. ***