This is an auto-filled bug because dev-libs/elfutils 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.
To reproduce this issue you may want to temporarily move the /usr/bin/cc - /usr/bin/gcc binaries.
Created attachment 634088 [details]
build log and emerge --info
I only see 2 tests trying to access 'gcc':
/var/tmp/portage/dev-libs/elfutils-0.179/work/elfutils-0.179/tests/run-strip-nothing.sh: line 26: gcc: command not found
FAIL run-strip-nothing.sh (exit status: 127)
Create debug a.out.
/var/tmp/portage/dev-libs/elfutils-0.179/work/elfutils-0.179/tests/run-strip-g.sh: line 28: gcc: command not found
FAIL run-strip-g.sh (exit status: 127)
The bug has been closed via the following commit(s):
Author: Sergei Trofimovich <email@example.com>
AuthorDate: 2020-05-30 21:58:04 +0000
Commit: Sergei Trofimovich <firstname.lastname@example.org>
CommitDate: 2020-05-30 21:58:04 +0000
dev-libs/elfutils: use $CC in tests consistently, bug #718872
Reported-by: Agostino Sarubbo
Package-Manager: Portage-2.3.100, Repoman-2.3.22
Signed-off-by: Sergei Trofimovich <email@example.com>
dev-libs/elfutils/elfutils-0.179.ebuild | 3 ++
.../files/elfutils-0.179-CC-in-tests.patch | 45 ++++++++++++++++++++++
2 files changed, 48 insertions(+)
Proposed patch upstream as https://sourceware.org/pipermail/elfutils-devel/2021q1/003425.html