This is an auto-filed bug because sys-fabric/libibumad calls cc 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 CC implementation (like clang) by setting the CC variable. So this issue has been reproduced by setting the CC variable to x86_64-pc-linux-gnu-gcc and by removing the /usr/bin/cc - /usr/bin/gcc binaries.
Created attachment 642302 [details]
build log and emerge --info
The bug has been closed via the following commit(s):
Author: Jakov Smolić <email@example.com>
AuthorDate: 2022-02-15 09:18:30 +0000
Commit: Jakov Smolić <firstname.lastname@example.org>
CommitDate: 2022-02-15 09:22:44 +0000
Signed-off-by: Jakov Smolić <email@example.com>
profiles/package.mask | 1 -
sys-fabric/libibumad/Manifest | 1 -
sys-fabric/libibumad/libibumad-1.3.9.ebuild | 30 -----------------------------
sys-fabric/libibumad/metadata.xml | 13 -------------
4 files changed, 45 deletions(-)