This is an auto-filled bug because app-crypt/princeprocessor 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 637450 [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=021a252a945d8eccf702d7703c2904a35cdad18f commit 021a252a945d8eccf702d7703c2904a35cdad18f Author: Michael Mair-Keimberger <mmk@levelnine.at> AuthorDate: 2023-12-31 17:56:38 +0000 Commit: Conrad Kostecki <conikost@gentoo.org> CommitDate: 2024-03-16 12:13:28 +0000 app-crypt/princeprocessor: EAPI8 bump, fix calling cc directly, bug #722044 Signed-off-by: Michael Mair-Keimberger <mmk@levelnine.at> Closes: https://bugs.gentoo.org/722044 Closes: https://github.com/gentoo/gentoo/pull/34587 Signed-off-by: Conrad Kostecki <conikost@gentoo.org> .../princeprocessor/princeprocessor-0.22-r1.ebuild | 27 ++++++++++++++++++++++ 1 file changed, 27 insertions(+)