On Apr 6, 2005 1:41 PM, Bradley Serbu <[EMAIL PROTECTED]> wrote:Bradley,
brads $ sudo fix_libtool_files.sh 3.3.5
* Scanning libtool files for hardcoded gcc library paths...
Tried this and the command ran successfully, but didn't fix the error.
Christoph Gysin wrote:
>Bradley Serbu wrote:
>>Ok, looks like the no such directory at the bottom, but I included a
>>bunch more incase I'm missing something else...
>>grep: //usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5/libstdc++.la: No such
>>file or directory
>>/bin/sed: can't read
>>//usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5/libstdc++.la: No such file or
>>libtool: link: `//usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5/libstdc++.la'
>>is not a valid libtool archive
>The bug was an incorrect gcc version check in an eclass. The following
>line should solve your problem.
>$ fix_libtool_files.sh 3.3.5
email@example.com mailing list
I always search the forums and bugzilla, but it is really all about figuring out what to search for. I think if you recently upgraded gcc, since you appear to running gcc 3.3.5 you may have to run fix_libtool_files-sh 3.3.4. I have not had the problem you are running into since I upgraded to 3.3.5. Anyways I hope this helps.