This is an auto-filled bug because dev-libs/concurrencykit calls ar directly.
The issue was originally discovered on amd64, but it may be reproducible on other arches as well.
If you think that a different summary clarifies the issue better, feel free to change it.
Attached build log and emerge --info.
If you think it doesn't make sense fix these type of issues, I'd like to point out that won't be possible use a different AR implementation (like llvm-ar) by setting the AR variable. So this issue has been reproduced by setting the AR variable to x86_64-pc-linux-gnu-ar and by removing the /usr/bin/ar binary.
Created attachment 637142 [details]
build log and emerge --info
Upstream accepted my patch.
The bug has been closed via the following commit(s):
Author: Conrad Kostecki <email@example.com>
AuthorDate: 2020-11-22 01:47:55 +0000
Commit: Conrad Kostecki <firstname.lastname@example.org>
CommitDate: 2020-11-22 01:50:36 +0000
dev-libs/concurrencykit: fixed several bugs
This is a overhaul of the whole ebuild. Nothing will change for the
user, so I will keep the stable keyword for amd64, as I will drop 0.7.0
1) Fixed calling AR - upstream accepted patch.
2) Failing tests on x86 - Setting PROFILE correctly.
3) Disabling static libs - upstream accepted patch.
4) Updated patches to use from upstreams git.
Package-Manager: Portage-3.0.9, Repoman-3.0.2
Signed-off-by: Conrad Kostecki <email@example.com>
.../concurrencykit/concurrencykit-0.7.0-r1.ebuild | 40 ++++++++
.../files/concurrencykit-0.7.0-ar.patch | 112 +++++++++++++++++++++
.../files/concurrencykit-0.7.0-glibc-2.30.patch | 54 ++++++++++
.../files/concurrencykit-0.7.0-gzip.patch | 58 +++++++++++
.../files/concurrencykit-0.7.0-static-libs.patch | 75 ++++++++++++++
5 files changed, 339 insertions(+)