This is an auto-filled bug because dev-ml/camldbm calls ranlib 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 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 639128 [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=2b4dbdea0d25239a573a329efeeaaff8a88794f5 commit 2b4dbdea0d25239a573a329efeeaaff8a88794f5 Author: Alfredo Tupone <tupone@gentoo.org> AuthorDate: 2022-01-22 13:43:12 +0000 Commit: Alfredo Tupone <tupone@gentoo.org> CommitDate: 2022-01-22 13:43:12 +0000 dev-ml/camldbm: do not call ranlib directly Closes: https://bugs.gentoo.org/723142 Package-Manager: Portage-3.0.28, Repoman-3.0.3 Signed-off-by: Alfredo Tupone <tupone@gentoo.org> dev-ml/camldbm/camldbm-1.0.ebuild | 12 +++++++++++- dev-ml/camldbm/camldbm-1.2.ebuild | 12 +++++++++++- 2 files changed, 22 insertions(+), 2 deletions(-)
