https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-cpp/pystring-1.1.3 calls g++ directly. Discovered on: amd64 (internal ref: ci) NOTE: This machine uses GCC-11: https://gcc.gnu.org/gcc-11/porting_to.html 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 C++ implementation (like clang++). To reproduce, please use sys-devel/gcc-config[-native-symlinks], sys-devel/binutils-config[-native-symlinks].
Created attachment 715041 [details] build.log build log and emerge --info
Possible context of error(s): /usr/bin/libtool: line 1813: g++: command not found
I've posted a fix here: https://github.com/gentoo/gentoo/pull/21209
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=91773fd1eb57d4c080c0151f5899f1631ddf2aac commit 91773fd1eb57d4c080c0151f5899f1631ddf2aac Author: Sebastian Parborg <darkdefende@gmail.com> AuthorDate: 2021-06-12 12:00:18 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-06-12 12:54:54 +0000 dev-cpp/pystring: Don't use hardcoded g++ (convert to CMake) Convert the project into cmake so we get compiler switching for free. Closes: https://bugs.gentoo.org/795156 Closes: https://bugs.gentoo.org/795168 Signed-off-by: Sebastian Parborg <darkdefende@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/21209 Signed-off-by: Sam James <sam@gentoo.org> dev-cpp/pystring/files/cmake.patch | 84 ++++++++++++++++++++++ ...tring-1.1.3.ebuild => pystring-1.1.3-r1.ebuild} | 20 ++---- 2 files changed, 91 insertions(+), 13 deletions(-)
