> > I've tried the command given above, and while it generates some output, > > building continues to fail with the same error. > > > > [EMAIL PROTECTED] ~] fix_libtool_files.sh 3.3.4 > > * Scanning libtool files for hardcoded gcc library paths... > > * [1/5] Scanning /lib ... > > * [2/5] Scanning /usr/lib ... > > * [3/5] Scanning /usr/kde/3.3/lib ... > > * [4/5] Scanning /usr/local/lib ... > > * [5/5] Scanning /usr/qt/3/lib ... > > What's the output of gcc-config -l (that's a small L, not i) > > for example, mine is: > > [EMAIL PROTECTED] ~ $ gcc-config -l > [1] i686-pc-linux-gnu-3.3.4 > [2] i686-pc-linux-gnu-3.4.3-20050110 * > [3] i686-pc-linux-gnu-3.4.3-20050110-hardened > [4] i686-pc-linux-gnu-3.4.3-20050110-hardenednopie > [5] i686-pc-linux-gnu-3.4.3-20050110-hardenednossp
[EMAIL PROTECTED] /usr/lib/gcc-lib] gcc-config -l [1] i686-pc-linux-gnu-3.3.5 * [2] i686-pc-linux-gnu-3.3.5-hardened [3] i686-pc-linux-gnu-3.3.5-hardenednopie [4] i686-pc-linux-gnu-3.3.5-hardenednossp > > When you do the fix_libtool_files.sh x.x.x thing, you need to refer to the > gcc version previously used, not the current one- at least that's what > worked for me. I think I did. > -- > [email protected] mailing list -- [email protected] mailing list
