This is an auto-filled bug because dev-libs/libowfat 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 639002 [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=980727e322ee68cd912a2f00f491d3eb77d09f67 commit 980727e322ee68cd912a2f00f491d3eb77d09f67 Author: Rolf Eike Beer <eike@sf-mail.de> AuthorDate: 2021-08-20 13:10:28 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-08-22 03:07:08 +0000 dev-libs/libowfat: respect ar and ranlib settings from toolchain Closes: https://bugs.gentoo.org/723036 Signed-off-by: Rolf Eike Beer <eike@sf-mail.de> Closes: https://github.com/gentoo/gentoo/pull/22048 Signed-off-by: Sam James <sam@gentoo.org> dev-libs/libowfat/files/libowfat-0.32-ar.patch | 66 ++++++++++++++++++++++ ...wfat-0.32-r3.ebuild => libowfat-0.32-r4.ebuild} | 3 + 2 files changed, 69 insertions(+)