This is an auto-filled bug because app-misc/linux-logo calls cc directly. The issue was originally discovered on arm64, but it may be reproducible on other arches as well. Attached build log and emerge --info. NOTE: To reproduce this issue you may want to temporarily move the /usr/bin/cc - /usr/bin/gcc binaries.
Created attachment 633736 [details] build.log build log and emerge --info
OK, this was partially fixed before apparently, with src_compile() using correct CC, but not src_configure(). I will try to make it set correctly from configure step (and just leave default compilation after that)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8124fadf4a2b629eecb56a06edd6f2f383beb233 commit 8124fadf4a2b629eecb56a06edd6f2f383beb233 Author: Bernard Cafarelli <voyageur@gentoo.org> AuthorDate: 2020-04-23 21:44:26 +0000 Commit: Bernard Cafarelli <voyageur@gentoo.org> CommitDate: 2020-04-23 21:55:47 +0000 app-misc/linux-logo: set CC and flags directly in configure Previously, this was set only from src_compile(), which can cause incorrcet flags being added at configure run (custom script) Closes: https://bugs.gentoo.org/718370 Package-Manager: Portage-2.3.99, Repoman-2.3.22 Signed-off-by: Bernard Cafarelli <voyageur@gentoo.org> .../files/linux-logo-5.11-configure.patch | 78 +++++++++++++++++++++ app-misc/linux-logo/linux-logo-5.11-r5.ebuild | 80 ++++++++++++++++++++++ 2 files changed, 158 insertions(+)
