On Thu, 17 Feb 2005 22:22:04 +0000, Etaoin Shrdlu <[EMAIL PROTECTED]> wrote: > On Thursday 17 February 2005 21:09, Mark Knecht wrote: > > > Hi again, > > OK, I was another 90 minutes into the last 156 and it failed > > somewhere around #60 with the following failure: > > > > grep: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la: No such > > file or directory > > sed: can't read /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la: > > No such file or directory > > libtool-disable-static: link: > > `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la' is not a valid > > libtool archive > > This is a possible candidate for "the most asked question of the last > weeks" :) > > I think you have to issue (as root) a > > fix_libtool_files.sh 3.3.4 > > and then the error should go away.
Thanks. You're clue led to this Gentoo page http://gentoo-wiki.com/HOWTO_Migrate_to_GCC_3.4 I'm a bit confused why this is occuring for gcc-3.3.5 but I'm happy for the help. Thanks. It is proceeding. Guess I should read the list more closely. I've been busy and not paying much attention. It looks like the emerge --resume skipped the flac package that originally failed so I'll go back and pick that one up by hand I guess. I presume that the 180 packages that emerged before this one are not effected by this gcc change? Thanks, Mark -- [email protected] mailing list
