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. NOTE: 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 build log and emerge --info
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bcd1e284afaeae01d6fd65d06e5e2d9f6dcc9f9c commit bcd1e284afaeae01d6fd65d06e5e2d9f6dcc9f9c Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2020-12-22 16:24:24 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2020-12-22 16:28:59 +0000 app-backup/tarsnap: respect AR Closes: https://bugs.gentoo.org/721914 Package-Manager: Portage-3.0.12, Repoman-3.0.2 Signed-off-by: Thomas Deutschmann <whissi@gentoo.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(-)