This is an auto-filled bug because app-crypt/libscrypt calls ar directly. The issue was originally discovered on arm64, but it may be reproducible on other arches as well. Attached build log and emerge --info. NOTE: To reproduce this issue you may want to temporarily move the /usr/bin/ar binary.
Created attachment 633656 [details] build.log build log and emerge --info
ci has reproduced this issue with version 1.21 - Updating summary.
ci has reproduced this issue with version 1.22 - Updating summary.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7497b5d60f22700ebb72c0ecdfff2be10b381bd3 commit 7497b5d60f22700ebb72c0ecdfff2be10b381bd3 Author: Michael Mair-Keimberger <mmk@levelnine.at> AuthorDate: 2023-12-30 16:48:58 +0000 Commit: Conrad Kostecki <conikost@gentoo.org> CommitDate: 2024-01-07 00:19:33 +0000 app-crypt/libscrypt: don't call ar directly, fix #718126 Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at> Closes: https://bugs.gentoo.org/718126 Closes: https://github.com/gentoo/gentoo/pull/34566 Signed-off-by: Conrad Kostecki <conikost@gentoo.org> app-crypt/libscrypt/libscrypt-1.22-r2.ebuild | 36 ++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+)