This is an auto-filed bug because net-libs/libecap 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 641278 [details]
build log and emerge --info
The bug has been closed via the following commit(s):
Author: Sam James <firstname.lastname@example.org>
AuthorDate: 2021-02-27 02:20:40 +0000
Commit: Sam James <email@example.com>
CommitDate: 2021-02-27 02:24:59 +0000
net-libs/libecap: bump to 1.0.1
Package-Manager: Portage-3.0.15, Repoman-3.0.2
Signed-off-by: Sam James <firstname.lastname@example.org>
net-libs/libecap/Manifest | 1 +
net-libs/libecap/libecap-1.0.1.ebuild | 35 +++++++++++++++++++++++++++++++++++
2 files changed, 36 insertions(+)