This is an auto-filed bug because sys-power/nvclock 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 642458 [details]
build log and emerge --info
The bug has been closed via the following commit(s):
Author: David Seifert <firstname.lastname@example.org>
AuthorDate: 2020-08-29 17:33:53 +0000
Commit: David Seifert <email@example.com>
CommitDate: 2020-08-29 17:33:53 +0000
sys-power/nvclock: Port to EAPI 7
Package-Manager: Portage-3.0.4, Repoman-3.0.1
Signed-off-by: David Seifert <firstname.lastname@example.org>
.../files/nvclock-0.8_p20110102-fno-common.patch | 11 ++
.../files/nvclock-0.8_p20110102-r1-make.patch | 135 +++++++++++++++------
sys-power/nvclock/nvclock-0.8_p20110102-r2.ebuild | 36 +++---
3 files changed, 129 insertions(+), 53 deletions(-)