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. NOTE: 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 build log and emerge --info
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=579837335f65c3428943bf95f5fbb73457558187 commit 579837335f65c3428943bf95f5fbb73457558187 Author: Jakov Smolić <jsmolic@gentoo.org> AuthorDate: 2022-02-15 09:18:30 +0000 Commit: Jakov Smolić <jsmolic@gentoo.org> CommitDate: 2022-02-15 09:22:44 +0000 sys-fabric/libibumad: treeclean Closes: https://bugs.gentoo.org/725838 Signed-off-by: Jakov Smolić <jsmolic@gentoo.org> 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(-)