kdebase-3.0.4-r3 ebuild fails with the following error: i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/kde/3/include -I/usr/qt/3/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -DNDEBUG -DNO_DEBUG -O2 -march=pentium4 -Os -pipe -s -fexpensive-optimizations -ffast-math -fomit-frame-pointer -fno-exceptions -fno-check-new -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT -DQT_NO_ASCII_CAST -c kded_favicons_la.all_cpp.cpp -fPIC -DPIC -o .libs/kded_favicons_la.all_cpp.o /bin/sh ../../libtool --mode=link --tag=CXX i686-pc-linux-gnu-g++ -DNDEBUG -DNO_DEBUG -O2 -march=pentium4 -Os -pipe -s -fexpensive-optimizations -ffast-math -fomit-frame-pointer -fno-exceptions -fno-check-new -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT -DQT_NO_ASCII_CAST -o kded_favicons.la -rpath /usr/kde/3/lib/kde3 -L/usr/X11R6/lib -L/usr/qt/3/lib -L/usr/kde/3/lib -module -avoid-version kded_favicons_la.all_cpp.lo -lkio grep: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2/libstdc++.la: No such file or directory sed: can't read /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2/libstdc++.la: No such file or directory libtool: link: `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2/libstdc++.la' is not a valid libtool archive make[3]: *** [kded_favicons.la] Error 1 make[3]: Leaving directory `/var/tmp/portage/kdebase-3.0.4-r3/work/kdebase-3.0.4/libkonq/favicons' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/kdebase-3.0.4-r3/work/kdebase-3.0.4/libkonq' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/kdebase-3.0.4-r3/work/kdebase-3.0.4' make: *** [all] Error 2 !!! ERROR: kde-base/kdebase-3.0.4-r3 failed. !!! Function kde_src_compile, Line 88, Exitcode 2 !!! died running emake, kde_src_compile:make I have gcc-3.2.1 and libtool-1.4.1-r10. I am not familiar with libtool but notice that it is referring to a path /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2/libstdc++.la and instead since I'm on gcc-3.2.1, I have /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/libstdc++.la Anything else I can provide for further investigation?
*** This bug has been marked as a duplicate of 11094 ***