@@This is an auto-filed bug@@ If you think that a different summary clarifies the issue better, feel free to change it. Issue: dev-ml/labltk calls ranlib directly. Discovered on: amd64 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 RANLIB implementation (like llvm-ranlib) by setting the RANLIB variable. So this issue has been reproduced by setting the RANLIB variable to x86_64-pc-linux-gnu-ranlib and by removing the /usr/bin/ranlib binary.
Created attachment 643560 [details] build.log build log and emerge --info
ci has reproduced this issue with version 8.06.10 - Updating summary.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=04567015f131419f60a5c5e4afa21fadb788e4d0 commit 04567015f131419f60a5c5e4afa21fadb788e4d0 Author: Alfredo Tupone <tupone@gentoo.org> AuthorDate: 2022-01-21 22:05:01 +0000 Commit: Alfredo Tupone <tupone@gentoo.org> CommitDate: 2022-01-21 22:05:01 +0000 dev-ml/labltk: do not call ranlib directly Closes: https://bugs.gentoo.org/727250 Package-Manager: Portage-3.0.28, Repoman-3.0.3 Signed-off-by: Alfredo Tupone <tupone@gentoo.org> dev-ml/labltk/labltk-8.06.10.ebuild | 6 +++++- dev-ml/labltk/labltk-8.06.11.ebuild | 10 ++++++---- dev-ml/labltk/labltk-8.06.7.ebuild | 13 +++++++++++-- dev-ml/labltk/labltk-8.06.9.ebuild | 12 ++++++++++-- 4 files changed, 32 insertions(+), 9 deletions(-)
