This is an auto-filed bug because sys-libs/libieee1284 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 641590 [details]
build log and emerge --info
The bug has been closed via the following commit(s):
Author: Thomas Deutschmann <firstname.lastname@example.org>
AuthorDate: 2020-09-01 10:33:53 +0000
Commit: Thomas Deutschmann <email@example.com>
CommitDate: 2020-09-01 10:43:35 +0000
sys-libs/libieee1284: don't call CC directly
Package-Manager: Portage-3.0.4, Repoman-3.0.1
Signed-off-by: Thomas Deutschmann <firstname.lastname@example.org>
sys-libs/libieee1284/libieee1284-0.2.11-r7.ebuild | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)