https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: net-misc/kea-2.4.1 fails to compile. Discovered on: amd64 (internal ref: clang-lld_tinderbox) System: CLANG-LLD (https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#CLANG-LLD) Info about the issue: https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#CF0014
Created attachment 886671 [details] build.log build log and emerge --info
Created attachment 886672 [details] 1-config.log 1-config.log
Created attachment 897757 [details, diff] avoid adding /usr/lib its configure.ac add /usr/lib (along with /usr/lib64) to library search path, clang assume -m32 arch. patch to avoid searching /usr (/lib*) since it's already system default
[ebuild N ] dev-libs/log4cplus-2.0.7:0/3::gentoo USE="iconv threads -explicit-initialization -qt5 -server -test" 910 KiB [ebuild N ~] net-misc/kea-2.4.1::gentoo USE="filecaps mysql openssl samples -debug -doc -postgres -shell -test" PYTHON_SINGLE_TARGET="python3_12 -python3_11" 10,242 KiB
(In reply to Jaco Kroon from comment #4) > [ebuild N ] dev-libs/log4cplus-2.0.7:0/3::gentoo USE="iconv threads > -explicit-initialization -qt5 -server -test" 910 KiB > [ebuild N ~] net-misc/kea-2.4.1::gentoo USE="filecaps mysql openssl > samples -debug -doc -postgres -shell -test" PYTHON_SINGLE_TARGET="python3_12 > -python3_11" 10,242 KiB This bug is NOT about a missing dependency. It's specific to using lld (or any linker which errors out, rather than warning, on incompatible objects). The issue is that they do e.g. `gcc ... -L/usr/lib a.o`, then the linker sees incompatible objects in /usr/lib (like libc.so) and aborts rather than warning and looking in the default search locations.
(In reply to Sam James from comment #5) > This bug is NOT about a missing dependency. It's specific to using lld (or > any linker which errors out, rather than warning, on incompatible objects). > > The issue is that they do e.g. `gcc ... -L/usr/lib a.o`, then the linker > sees incompatible objects in /usr/lib (like libc.so) and aborts rather than > warning and looking in the default search locations. My bad, I completely mis-read this. Was hoping to file a stabilization bug, but plainly it's not ready except in niche cases, and for people willing to suffer a few issues.
It may well not be a regression, though.