See URL for details. See http://www.lyndir.com/stuff/info for emerge --info Basically, a massive repetition of errors such as this: /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include/g++-v4/bits/basic_string.h:230: undefined reference to `std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Rep::_S_empty_rep_storage' Reproducible: Always Steps to Reproduce:
Already tried recompiling with CXXFLAGS=$CFLAGS and these problems existed even before the existance of my LDFLAGS. Also tried recompiling the toolchain before recompiling this package; all with the default CXXFLAGS. .. Didn't try emerge -e world with the default CXXFLAGS, but unless there is an understandable reason behind suggesting this; I find this solution quite rediculous (it was suggested to me in #gentoo).
http://www.gentoo.org/doc/en/gcc-upgrading.xml *** This bug has been marked as a duplicate of bug 64615 ***
Did: emerge -1 libtool sys-libs/libstdc++-v3 && revdep-rebuild --library libstdc++.so.5 Problem unresolved. Did: /var/db/pkg # grep '^GCC_PATH' <(bunzip2 -c */*/environment.bz2) Returns GCC_PATH=/usr/i686-pc-linux-gnu/gcc-bin/4.1.2 for ALL packages.
(In reply to comment #3) > Problem unresolved. You should re-read the howto, first of all. Then follow it. *** This bug has been marked as a duplicate of bug 64615 ***
I just did an emerge -e system which compiled about 300 packages. After that, slim still did not compile (same errors). emerge -e slim does not contain any packages that were not recompiled with emerge -e system (except for coreutils which is totally irrelevant). Now, either you were too quick to judge this bug or I lack the understanding to see what you mean for me to do by telling me to follow that howto. Either way, this bug needs closer attention. In the latter case, try to be a little less abstract. fix_libtool_files.sh 3.4.6; fix_libtool_files.sh 4.1.1 does not find anything in need of fixing; just in case it's relevant.
Please, stop reopening this bug; the issue is your broken gcc upgrade, not the ebuilds. Leave this alone; thanks. *** This bug has been marked as a duplicate of bug 64615 ***
