Ben Ricker ([EMAIL PROTECTED]) scribbled: > I have had the following issue on numerous emerges. It looks like > something in libstdc++ is fragged. Here is the error I have received > on 5 emerges. The two that I recall it happening on is gnome-vfs and > k3b. > > This is the traceback from the gnome-vfs emerge failure: > > creating libnetwork.la > powerpc-unknown-linux-gnu-ar cru .libs/libfile.a file-method.o fstype.o > powerpc-unknown-linux-gnu-ranlib .libs/libfile.a > creating libfile.la > /bin/sed: can't read > /usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.1/libstdc++.la: No such > file or directory > libtool: link: `/usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.1/libstdc++.la' > is not a valid libtool archive > make[3]: *** [libfile.la] Error 1 > make[3]: *** Waiting for unfinished jobs.... > (cd .libs && rm -f libnetwork.la && ln -s ../libnetwork.la libnetwork.la) > snip..... > > Any ideas? I am running libstdc++-V3 vers 3.4.4.
Before the flames start, search for 'fix_libtool_files.sh' in the archives/google. This is a frequent problem due to hardcoded version numbers. # fix_libtools_files.sh <version> hth, Cooper. -- [email protected] mailing list
