@@This is an auto-filed bug@@ If you think that a different summary clarifies the issue better, feel free to change it. Issue: app-editors/jasspa-microemacs calls cc directly. Discovered on: amd64 NOTE: As per QA policy, toolchain tools must not be called directly because they can cause issue in cross-compiling and because is not possible use a different CC implementation (like clang). To reproduce, please use sys-devel/gcc-config[-native-symlinks], sys-devel/binutils-config[-native-symlinks] and set the CC variable to x86_64-pc-linux-gnu-gcc.
Created attachment 645812 [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=254c16078eddcf4c41abe1d807218494ac831b15 commit 254c16078eddcf4c41abe1d807218494ac831b15 Author: Ulrich Müller <ulm@gentoo.org> AuthorDate: 2020-06-23 09:01:17 +0000 Commit: Ulrich Müller <ulm@gentoo.org> CommitDate: 2020-06-23 10:46:18 +0000 app-editors/jasspa-microemacs: Do not try to detect cc or gcc. Closes: https://bugs.gentoo.org/729258 Package-Manager: Portage-2.3.101, Repoman-2.3.22 Signed-off-by: Ulrich Müller <ulm@gentoo.org> .../files/20091011-cc-detect.patch | 32 ++++++++++++++++++++++ .../jasspa-microemacs-20091011-r3.ebuild | 3 +- 2 files changed, 34 insertions(+), 1 deletion(-)