This is an auto-filed bug because sys-apps/edac-utils 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 641958 [details]
build log and emerge --info
The bug has been closed via the following commit(s):
Author: Sam James <firstname.lastname@example.org>
AuthorDate: 2021-08-02 03:00:14 +0000
Commit: Sam James <email@example.com>
CommitDate: 2021-08-02 03:17:09 +0000
sys-apps/edac-utils: install init script/systemd unit, CC fix
1) The previous revision mentioned udev but the udev rule
was dropped upstream quite some time ago as it was found
to be unreliable.
We now install an init script and a systemd unit to load
the edac rules. The simple systemd unit was nabbed from Fedora.
2) We now call eautoreconf in order to refesh libtool and friends
to fix calling gcc directly.
Signed-off-by: Sam James <firstname.lastname@example.org>
sys-apps/edac-utils/edac-utils-0.18-r1.ebuild | 53 +++++++++++++++++++++++++++
sys-apps/edac-utils/files/edac.init | 16 ++++++++
sys-apps/edac-utils/files/edac.service | 11 ++++++
3 files changed, 80 insertions(+)