This is an auto-filled bug because app-backup/tarsnap 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 637128 [details]
build log and emerge --info
The bug has been closed via the following commit(s):
Author: Thomas Deutschmann <firstname.lastname@example.org>
AuthorDate: 2020-12-22 16:24:24 +0000
Commit: Thomas Deutschmann <email@example.com>
CommitDate: 2020-12-22 16:28:59 +0000
app-backup/tarsnap: respect AR
Package-Manager: Portage-3.0.12, Repoman-3.0.2
Signed-off-by: Thomas Deutschmann <firstname.lastname@example.org>
app-backup/tarsnap/files/tarsnap-1.0.39-respect-AR.patch | 14 ++++++++++++++
app-backup/tarsnap/tarsnap-1.0.39.ebuild | 10 ++++++++--
2 files changed, 22 insertions(+), 2 deletions(-)