This is an auto-filled bug because dev-ml/zarith 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 639130 [details]
build log and emerge --info
The bug has been closed via the following commit(s):
Author: Alfredo Tupone <firstname.lastname@example.org>
AuthorDate: 2020-05-17 16:00:24 +0000
Commit: Alfredo Tupone <email@example.com>
CommitDate: 2020-05-17 16:00:24 +0000
dev-ml/zarith: using AR
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Alfredo Tupone <firstname.lastname@example.org>
dev-ml/zarith/files/zarith-1.9.1-ar.patch | 11 +++++++++++
dev-ml/zarith/zarith-1.9.1.ebuild | 6 +++++-
2 files changed, 16 insertions(+), 1 deletion(-)