https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: app-crypt/reop-2.1.1 calls cc directly. Discovered on: amd64 (internal ref: guru_tinderbox) 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 701493 [details] build.log build log and emerge --info
Possible context of error(s): make: cc: No such file or directory
Changing the Assignee as per https://archives.gentoo.org/gentoo-dev/message/74ee632e9fe2f4c12890524fec132205
Your build.log says "Unset: CC", which seems incorrect in this case. The ebuild is using `emake CC=${CC:-cc} …` so it should be correct, it is expecting to fallback to gcc instead?
Changing TRACKER as requested by QA.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=d592068f9dbdfd5963859ca7a6d26002f1b6f9e0 commit d592068f9dbdfd5963859ca7a6d26002f1b6f9e0 Author: Anna Vyalkova <cyber@sysrq.in> AuthorDate: 2021-05-16 12:12:57 +0000 Commit: Anna Vyalkova <cyber@sysrq.in> CommitDate: 2021-05-16 14:05:01 +0000 app-crypt/reop: properly set CC variable Closes: https://bugs.gentoo.org/784791 Signed-off-by: Anna Vyalkova <cyber@sysrq.in> app-crypt/reop/reop-2.1.1.ebuild | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
