Allan Spagnol Comar schreef: > I am having this problem for 4 days now, I believe I made a sin by > changing my CHOST from pentium3 to i686 :( ...... every now and then I > am having this kind of message > > //usr/lib/gcc-lib/pentium3-pc-linux-gnu/3.3.5/libstdc++.la: No > such file or directory > /bin/sed: can't read > //usr/lib/gcc-lib/pentium3-pc-linux-gnu/3.3.5/libstdc++.la: No such file > or directory > libtool: link: > `//usr/lib/gcc-lib/pentium3-pc-linux-gnu/3.3.5/libstdc++.la' is not a > valid libtool archive > > > I already tryed all, I tryed: > > fix_libtool_files.sh 3.3.5 > fix_libtool_files.sh `gcc -dumpversion` --oldarch pentium3-pc-linux-gnu > > What more can I do ?
You can re-emerge libtool. Sometimes that works when fix_libtool_files does not. You could also try re-emerging libstdc++-v3 as well. I suspect there might be more you should (have) re-compile(d) after making a change to CHOST, but I've never done that, so I couldn't say what more you might need to re-emerge for stability's sake. I do feel we just talked about this issue on the list not too long ago, though, so you might want to check the archives for the past two weeks or so and see if there are any tips to be found. > > please I am hopeless at this point ;( > Then I hope this helps :) Holly -- gentoo-user@gentoo.org mailing list
