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.
- Brad
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
directory
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
Christoph
-- gentoo-user@gentoo.org mailing list
