This is an auto-filed bug because sci-libs/libint 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 641844 [details]
build log and emerge --info
The bug has been closed via the following commit(s):
Author: Jakov Smolic <firstname.lastname@example.org>
AuthorDate: 2021-05-25 18:02:51 +0000
Commit: Sam James <email@example.com>
CommitDate: 2021-05-26 12:35:22 +0000
sci-libs/libint: Fix direct ranlib call
Signed-off-by: Jakov Smolic <firstname.lastname@example.org>
Signed-off-by: Sam James <email@example.com>
sci-libs/libint/libint-2.6.0-r4.ebuild | 3 +++
1 file changed, 3 insertions(+)