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. 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 641590 [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=37c00365bbb7478a4a1332b42348ce5dd4b62dc8 commit 37c00365bbb7478a4a1332b42348ce5dd4b62dc8 Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2020-09-01 10:33:53 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2020-09-01 10:43:35 +0000 sys-libs/libieee1284: don't call CC directly Closes: https://bugs.gentoo.org/725240 Package-Manager: Portage-3.0.4, Repoman-3.0.1 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> sys-libs/libieee1284/libieee1284-0.2.11-r7.ebuild | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
