I discovered this while trying to do a 'man yabootconfig' and encountered an error about a missing shared libstdc++ library. I then attempted to emerge libstdc++-v3 Reproducible: Always Steps to Reproduce: 1. man yabootconfig (not failure referencing missing libstdc++ lib) 2. emerge libstdc++-v3 3. fail... Actual Results: rebot boot # man yabootconfig /usr/bin/gtbl: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such fileor directory groff: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory sh: line 1: 16538 Broken pipe /bin/gunzip -c '/usr/share/man/man8/yabootconfig.8.gz' So I attempted to 'emerge libstdc++-v3' and received this error: >>> Source unpacked. nls QA Notice: USE Flag 'build' not in IUSE for sys-libs/libstdc++-v3-3.3.4 build ~ppc64 * CFLAGS=" -O2 -mcpu=7400 -pipe" * CXXFLAGS=" -O2 -mcpu=7400 -pipe" * Configuring libstdc++... *** This configuration is not supported in the following subdirectories: target-libffi target-libf2c target-boehm-gc target-zlib target-libjava zlib fastjar target-libobjc (Any other directories should still work fine.) Created "Makefile" in /var/tmp/portage/libstdc++-v3-3.3.4/work/build using "mt-frag" conftest.c: In function `main': conftest.c:1: error: insn does not satisfy its constraints: (jump_insn 29 28 30 0 (parallel [ (return) (use (reg:DI 65 lr)) ]) 574 {*return_internal_di} (nil) (expr_list:REG_DEAD (reg:SI 66 ctr) (nil))) conftest.c:1: internal compiler error: in copyprop_hardreg_forward_1, at regrename.c:1549 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://bugs.gentoo.org/> for instructions. Preprocessed source stored into /var/tmp/portage/libstdc++-v3-3.3.4/temp/ccY4ok1A.out file, please attach this toyour bugreport. *** The command 'gcc -o conftest -O2 -mcpu=7400 -pipe conftest.c' failed. *** You must set the environment variable CC to a working compiler. I am using this gcc: gcc (GCC) 3.4.3 (Gentoo Linux 3.4.3, ssp-3.4.3-0, pie-8.7.6.6) Copyright (C) 2004 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Expected Results: Should have compiled? I believe that an 'internal compiler error' should never happen. From my experience, that is usually indicative of a bug. Portage 2.0.51-r3 (default-ppc64-2004.3, gcc-3.4.1, glibc-2.3.4.20041102-r0, 2.6.9-G5 ppc64) ================================================================= System uname: 2.6.9-G5 ppc64 PPC970, altivec supported Gentoo Base System version 1.6.5 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.91.0.1 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r6 ACCEPT_KEYWORDS="ppc64 ~ppc64" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=G5 -maltivec -mabi=altivec -fno-strict-aliasing -pipe" CHOST="powerpc64-unknown-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=G5 -maltivec -mabi=altivec -fno-strict-aliasing -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks sandbox" GENTOO_MIRRORS="ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://mirror.datapipe.net/gentoo http://128.213.5.34/gentoo/ http://mirror.datapipe.net/gentoo" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="ppc64 X aim altivec apm arts berkdb bitmap-fonts crypt cups divx4linux encode ethereal foomaticdb gd gdbm gif gnome gpm gtk2 imlib jpeg kde libg++ libwww mad mikmod motif mozilla mpeg mysql ncurses nls oggvorbis oscar oss pam pdflib perl php png python qt quicktime readline samba sdl slang spell ssl tcpd truetype usb xinerama xml2 xmms zlib"
Thanks Jathan. As an FYI there wasa bug in past versions of gcc 3.3 it would appear (and i think it's fixed now I'm currently validating) where use of -mcpu would cause problems. Tho I've successfully been able to bootstrap using -mcpu now so I suspect the problem with gcc is fixed. For this bug I have also fixed libstdcxx. There were some assumptions being made that cause this ebuild to go south. Fixed.
stick a fork in it!
