This is an auto-filed bug because sci-libs/cdf 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 641832 [details] build.log build log and emerge --info
Created attachment 690075 [details] build log from running with CC="clang" Fixed with https://github.com/gentoo/gentoo/pull/19760
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2cdd21f573f85820be43dc8e2ca44730c269dcbe commit 2cdd21f573f85820be43dc8e2ca44730c269dcbe Author: Sam James <sam@gentoo.org> AuthorDate: 2021-07-29 02:13:01 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-07-29 02:13:25 +0000 sci-libs/cdf: fully respect AR, CC We were calling AR directly but also 'gcc' as LD. Let's just use $(tc-getCC) as LD given that's now the recommended way to call the linker, and indeed, we use incompatible arguments for ld anyway. Closes: https://bugs.gentoo.org/725444 Closes: https://bugs.gentoo.org/792990 Signed-off-by: Sam James <sam@gentoo.org> sci-libs/cdf/cdf-3.8.0-r1.ebuild | 2 ++ 1 file changed, 2 insertions(+)
