Harry Putnam <[EMAIL PROTECTED]> writes: >> The answer is in the original error message, 3.3.4 >> >> "grep: /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.4/libstdc++.la: No >> such file or directory" >> >>> Sounds pretty dumb but I >>> didn't see anything like a `history' item for qpkg or emerge. >> >> emerge genlop >> genlop gcc > > I must be missing something basic here. The version shown in that > output is the same version that is currently installed. > > Running genlop gcc produces: > > * sys-devel/gcc > > Wed Oct 27 17:25:47 2004 >>> sys-devel/gcc-3.3.4-r1 > Wed Oct 27 17:34:25 2004 >>> sys-devel/gcc-3.3.4-r1 > > So does it mean the same version was installed twice? > > Running ` fix_libtool_files.sh 3.3.4' > Doesn't seem to accomplish much either: > root # fix_libtool_files.sh 3.3.4 > * Scanning libtool files for hardcoded gcc library paths...
Ok, I tried running the command suggested in fix_libtool_files.sh `fix_libtool_files.sh `gcc -dumpversion` --oldarch i386-pc-linux-gnu Setting i386 as old target. And did see some `fixing' output on kde libs: * FIXING: /usr/lib/libaspell.la ... [c] * FIXING: /usr/lib/libpspell.la ... [c] So trying again with `emerge -v -k kdelibs' But I noticed that the portage tree does not contain my version of gcc gcc-3.3.4-r1 it jumps from 3.3.2 to 3.3.5 Is that significant? -- [email protected] mailing list
