This is an auto-filled bug because dev-db/cdb 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.
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 638372 [details]
build log and emerge --info
The bug has been closed via the following commit(s):
Author: Akinori Hattori <email@example.com>
AuthorDate: 2021-11-10 13:43:57 +0000
Commit: Akinori Hattori <firstname.lastname@example.org>
CommitDate: 2021-11-10 13:43:57 +0000
dev-db/cdb: do not call ranlib directly
Package-Manager: Portage-3.0.28, Repoman-3.0.3
Signed-off-by: Akinori Hattori <email@example.com>
dev-db/cdb/cdb-0.75-r4.ebuild | 1 +
1 file changed, 1 insertion(+)