This is an auto-filled bug because app-admin/cronolog 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 637120 [details] build.log build log and emerge --info
ci has reproduced this issue with version 1.6.2-r6 - Updating summary.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fa2962c4a96704f4ce86998995c53c2a0f86c260 commit fa2962c4a96704f4ce86998995c53c2a0f86c260 Author: Michael Mair-Keimberger <mmk@levelnine.at> AuthorDate: 2023-12-31 10:54:39 +0000 Commit: Conrad Kostecki <conikost@gentoo.org> CommitDate: 2024-01-07 00:19:32 +0000 app-admin/cronolog: fix calling ar directly, bug #721908 Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at> Closes: https://bugs.gentoo.org/721908 Closes: https://github.com/gentoo/gentoo/pull/34575 Signed-off-by: Conrad Kostecki <conikost@gentoo.org> app-admin/cronolog/cronolog-1.6.2-r7.ebuild | 30 +++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+)
