This is an auto-filed bug because www-apache/passenger 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 642482 [details]
build log and emerge --info
The bug has been closed via the following commit(s):
Author: Hans de Graaff <firstname.lastname@example.org>
AuthorDate: 2020-05-31 06:47:06 +0000
Commit: Hans de Graaff <email@example.com>
CommitDate: 2020-05-31 08:08:51 +0000
www-apache/passenger: add 6.0.5
Explicitly pass RANLIB.
Package-Manager: Portage-2.3.99, Repoman-2.3.22
Signed-off-by: Hans de Graaff <firstname.lastname@example.org>
www-apache/passenger/Manifest | 1 +
www-apache/passenger/passenger-6.0.5.ebuild | 130 ++++++++++++++++++++++++++++
2 files changed, 131 insertions(+)