checking for ANSI C header files... no checking for uintptr_t... no checking for pid_t... yes checking whether the C compiler ( /var/tmp/portage/sys-libs/libstdc++-v3-3.3.6-r4/work/build/gcc/xgcc -B/var/tmp/portage/sys-libs/libstdc++-v3-3.3.6-r4/work/build/gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -O2 -pipe -fno-diagnostics-color -O2 ) works... no configure: error: installation or configuration problem: C compiler cannot create executables. make: *** [Makefile:1351: configure-target-libiberty] Error 1 make: Leaving directory '/var/tmp/portage/sys-libs/libstdc++-v3-3.3.6-r4/work/build' ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_hardened-j4-20220123-140205 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.3.1 [2] x86_64-pc-linux-gnu-11.2.1 * clang/llvm (if any): /usr/lib/llvm/13 13.0.0 Python 3.9.10 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) [3] ruby30 (with Rubygems) * Available Rust versions: [1] rust-bin-1.58.1 * The Glorious Glasgow Haskell Compilation System, version 8.10.4 php cli: (none found) HEAD of ::gentoo commit 0459edbb67c0946b29b5610ddcad01702f6df568 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Mon Jan 24 23:37:30 2022 +0000 2022-01-24 23:37:27 UTC emerge -qpvO sys-libs/libstdc++-v3 [ebuild N ] sys-libs/libstdc++-v3-3.3.6-r4 USE="multilib nls"
Created attachment 763566 [details] emerge-info.txt
Created attachment 763567 [details] emerge-history.txt
Created attachment 763568 [details] environment
Created attachment 763569 [details] etc.portage.tar.bz2
Created attachment 763570 [details] logs.tar.bz2
Created attachment 763571 [details] sys-libs:libstdc++-v3-3.3.6-r4:20220125-003051.log.bz2
Created attachment 763572 [details] temp.tar.bz2
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ac3c099a82ddf6c98eab39db95c31e7d7db5e7df commit ac3c099a82ddf6c98eab39db95c31e7d7db5e7df Author: Eli Schwartz <eschwartz@gentoo.org> AuthorDate: 2024-09-24 02:58:46 +0000 Commit: Eli Schwartz <eschwartz@gentoo.org> CommitDate: 2024-09-25 03:17:03 +0000 sys-libs/libstdc++-v3: disable custom user flags entirely This is ancient brittle code -- an ancient, unmaintained version of GCC. It exists solely to provide access to an ancient, unmaintained version of libstdc++.so for ancient, unmaintained binaries that cannot be rebuilt. It doesn't need to be fast, or have cool CFLAGS. People shouldn't even be using it at all. The people who do use it care about compatibility more than anything else, so successfully compiling it should be taken as the gift that it is. With that in mind, we basically strip all flags. We preserve some existing logic to handle -march= values known to exist in this old gcc, and we continue to support -O levels, but we go no further. It's entirely impractical to support arbitrary flags, since every gcc release adds more flags that old versions don't support and then this fails because GCC 3's internal xgcc build cannot handle them. We also take this opportunity to add a workaround for modern C. New versions of GCC barf on some of the code here because it is not legal C99, but again, the point of this package is to provide legacy compatibility for ancient binaries, so... we assume if it ever worked before, it still works. :) Thus, suppress the errors. In order to suppress the errors, we make a wrapper script around the external compiler (not the xgcc one) so that we can apply flags that only affect modern compilers, and aren't parsed by xgcc which would choke on them due to those flags being too new. Closes: https://bugs.gentoo.org/879775 Closes: https://bugs.gentoo.org/919184 Closes: https://bugs.gentoo.org/832016 Closes: https://bugs.gentoo.org/923112 Signed-off-by: Eli Schwartz <eschwartz@gentoo.org> sys-libs/libstdc++-v3/libstdc++-v3-3.3.6-r4.ebuild | 75 +++++++++++----------- 1 file changed, 37 insertions(+), 38 deletions(-)
*** Bug 916270 has been marked as a duplicate of this bug. ***
*** Bug 909539 has been marked as a duplicate of this bug. ***
