This is an auto-filled bug because sys-process/runit calls ar directly. The issue was originally discovered on arm64, 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 aarch64-unknown-linux-gnu-ar and by removing the /usr/bin/ar binary.
Created attachment 637068 [details] build.log build log and emerge --info
the same happens for ranlib as showed in the build log.
Created attachment 639104 [details] make ar, ranlib configurable Here's a patch from my overlay against the runit 2.1.2 source that makes both ar and ranlib configurable by adding conf-ar and conf-ranlib files, similar to its existing conf-cc and conf-ld ones. With this fixing the ebuild should be fairly trivial.
Should this be marked dupe of bug 590412?
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0e256f242d7ce36744c2165fd639bebe7f9b6589 commit 0e256f242d7ce36744c2165fd639bebe7f9b6589 Author: Robin H. Johnson <robbat2@gentoo.org> AuthorDate: 2024-06-16 06:02:59 +0000 Commit: Robin H. Johnson <robbat2@gentoo.org> CommitDate: 2024-06-16 06:07:19 +0000 sys-process/runit: EAPI=8 porting and other fixes Signed-off-by: Robin H. Johnson <robbat2@gentoo.org> Closes: https://bugs.gentoo.org/show_bug.cgi?id=920357 Closes: https://bugs.gentoo.org/show_bug.cgi?id=875533 Closes: https://bugs.gentoo.org/show_bug.cgi?id=721880 Closes: https://bugs.gentoo.org/show_bug.cgi?id=590412 sys-process/runit/Manifest | 1 + sys-process/runit/runit-2.1.2-r2.ebuild | 149 ++++++++++++++++++++++++++++++++ 2 files changed, 150 insertions(+)
