It seems that when portage tries to build dev-libs/concurrencykit on x86, the package build system silently fails to build libck.so though it goes ahead and installs header files and documentation. When the makefile gets to this section: make -C src all || exit make[1]: Entering directory '/var/tmp/portage/dev-libs/concurrencykit-0.7.1/work/ck-0.7.1/src' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/var/tmp/portage/dev-libs/concurrencykit-0.7.1/work/ck-0.7.1/src' it thinks that it had no code to compile and silently fails the build. Workaround: If I remove this line from the ebuild: - $(usex x86 'export PROFILE=x86' '') the build will then compile and install. I can replicate the behavior in the raw tarball build if I set PROFILE=x86 and CC=gcc. This issue was detected when trying to build sys-apps/sysbench when it fails to build not able to find libck.so.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f1b56d18e6fb4361f96a1728d03a044b06f0698c commit f1b56d18e6fb4361f96a1728d03a044b06f0698c Author: Conrad Kostecki <conikost@gentoo.org> AuthorDate: 2021-07-23 19:23:56 +0000 Commit: Conrad Kostecki <conikost@gentoo.org> CommitDate: 2021-07-23 19:49:18 +0000 dev-libs/concurrencykit: fix x86 build Closes: https://bugs.gentoo.org/803248 Package-Manager: Portage-3.0.20, Repoman-3.0.3 Signed-off-by: Conrad Kostecki <conikost@gentoo.org> dev-libs/concurrencykit/concurrencykit-0.7.1.ebuild | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
