This is an auto-filled bug because dev-util/systemtap calls ar directly.
The issue was originally discovered on arm64, 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 aarch64-unknown-linux-gnu-ar and by removing the /usr/bin/ar binary.
Created attachment 635734 [details]
build log and emerge --info
The bug has been closed via the following commit(s):
Author: Sergei Trofimovich <email@example.com>
AuthorDate: 2020-09-08 22:58:23 +0000
Commit: Sergei Trofimovich <firstname.lastname@example.org>
CommitDate: 2020-09-08 22:58:28 +0000
dev-util/systemtap: respect user's AR
Reported-by: Agostino Sarubbo
Package-Manager: Portage-3.0.5, Repoman-3.0.1
Signed-off-by: Sergei Trofimovich <email@example.com>
dev-util/systemtap/files/systemtap-4.0-AR.patch | 11 +++++++++++
dev-util/systemtap/systemtap-4.0-r1.ebuild | 1 +
2 files changed, 12 insertions(+)
Proposed upstream as https://sourceware.org/pipermail/systemtap/2020q3/027024.html