My english is bad, sorry.... When I try emerge -U world, I get an error while kdelibs-3.3.0 is compliling. Reproducible: Always Steps to Reproduce: 1.emerge -U world 2. 3. Actual Results: ERROR: kde-base/kdelibs-3.3.0 failed. Expected Results: finish without errors grep: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4.3/libstdc++.la: No such file or directory /bin/sed: can't read /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4.3/libstdc++.la: No such file or directory libtool: link: `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4.3/libstdc++.la' is not a valid libtool archive make[3]: *** [libartskde.la] Error 1 make[3]: Leaving directory `/var/tmp/portage/kdelibs-3.3.0/work/kdelibs-3.3.0/arts/kde' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/kdelibs-3.3.0/work/kdelibs-3.3.0/arts' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/kdelibs-3.3.0/work/kdelibs-3.3.0' make: *** [all] Error 2 !!! ERROR: kde-base/kdelibs-3.3.0 failed. !!! Function kde_src_compile, Line 142, Exitcode 2 !!! died running emake, kde_src_compile:make libstdc++.la exist but in another directory: # ls /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/ cc1 include libstdc++.la cc1plus install-tools libstdc++.so collect2 libgcc.a libstdc++.so.5 crtbegin.o libgcc_eh.a libstdc++.so.5.0.6 crtbeginS.o libgcc_s.so libstdc++_pic.a crtbeginT.o libgcc_s.so.1 libsupc++.a crtend.o libiberty.a libsupc++.la crtendS.o libstdc++.a specs I'm newbee
/sbin/fix_libtool_files.sh and forums.gentoo.org are your friends.
Thanks!, I try this: /sbin/fix_libtool_files.sh 3.3.4.3 now I trying emerge -U world again....I'm sleepy now, I'm from venezuela so tomorrow I will see the results. Just a question, for learning...what /sbin/fix_libtool_files.sh really do?
It runs automatically at every gcc upgrade to fix the references to /usr/lib/gcc-lib/i686-pc-linux-gnu/ that are stored in ".la" library files (/usr/lib/*.la), but clearly something went wrong in your case...
Hey! Thanks! it works! I Think that the problem was solved
*** Bug 66483 has been marked as a duplicate of this bug. ***