On Thursday 17 February 2005 07:45 pm, David Corbin <[EMAIL PROTECTED]> wrote: > On Wednesday 16 February 2005 10:59 pm, Boyd Stephen Smith Jr. wrote: > > On Wednesday 16 February 2005 08:05 pm, David Corbin > > <[EMAIL PROTECTED]> wrote: > > > grep: /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.4/libstdc++.la: No such > > > file or directory > > > /bin/sed: can't read > > > /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.4/libstdc++.la: No such file > > > or directory
Probably; I wish it would learn to fix the libtool files automatically, but I'm betting that not trivial. FWIW, I really think the problem is with libtool, but I'm not exactly sure. > > Try fix_libtool_files.sh 3.3.4 as root. > > If that doesn't work try emerging libtool again, perhaps with emerge > > -1 libtool. > > I tried "fix_libtool_files", but that requires me to know lot more about > my "old configuration" (gcc, CHOST) than I really do. I tried the > emerge of libtool, but that did not help. Unless you've actively changed you CHOST (in make.conf) it hasn't changed, so you don't have to include that parameter. In the error message "/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.4/libstdc++.la: No such file or directory", 3.3.4 is your old version. You don't have to supply your new version to fix_libtool_files.sh. So, the command I specified "fix_libtool_files.sh 3.3.4", should be all your need to do. -- Boyd Stephen Smith Jr. [EMAIL PROTECTED] ICQ: 514984 YM/AIM: DaTwinkDaddy -- [email protected] mailing list
