This is an auto-filled bug because dev-libs/libmoe 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 638990 [details]
build log and emerge --info
The bug has been closed via the following commit(s):
Author: Akinori Hattori <firstname.lastname@example.org>
AuthorDate: 2020-06-16 14:06:19 +0000
Commit: Akinori Hattori <email@example.com>
CommitDate: 2020-06-16 14:11:41 +0000
dev-libs/libmoe: use tc-getRANLIB
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Akinori Hattori <firstname.lastname@example.org>
dev-libs/libmoe/libmoe-1.5.8-r3.ebuild | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)