This is an auto-filed bug because net-analyzer/barnyard 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 641250 [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=a01914a0c534358cc4440014d5277718412ee3a0 commit a01914a0c534358cc4440014d5277718412ee3a0 Author: Jeroen Roovers <jer@gentoo.org> AuthorDate: 2020-07-29 12:51:47 +0000 Commit: Jeroen Roovers <jer@gentoo.org> CommitDate: 2020-07-29 12:52:54 +0000 net-analyzer/barnyard: Old Package-Manager: Portage-3.0.1, Repoman-2.3.23 Closes: https://bugs.gentoo.org/show_bug.cgi?id=724860 Signed-off-by: Jeroen Roovers <jer@gentoo.org> net-analyzer/barnyard/Manifest | 1 - net-analyzer/barnyard/barnyard-0.2.0-r5.ebuild | 92 ------------------------- net-analyzer/barnyard/files/barnyard.64bit.diff | 81 ---------------------- 3 files changed, 174 deletions(-)