This is an auto-filed bug because dev-python/apsw 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 640116 [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=4bd082dcbaa5201a00383fd0e679f6b4c03f203d commit 4bd082dcbaa5201a00383fd0e679f6b4c03f203d Author: Zamarin Arthur <arthurzam@gmail.com> AuthorDate: 2021-05-22 17:53:15 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2021-05-30 16:59:26 +0000 dev-python/apsw: add 3.35.4_p1, bump to python 3.10 fix direct CC call passes tests Closes: https://bugs.gentoo.org/704606 Closes: https://bugs.gentoo.org/723726 Signed-off-by: Zamarin Arthur <arthurzam@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/20936 Signed-off-by: Michał Górny <mgorny@gentoo.org> dev-python/apsw/Manifest | 1 + dev-python/apsw/apsw-3.35.4_p1.ebuild | 46 +++++++++++++++++++++++++++++++++++ 2 files changed, 47 insertions(+)
