vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello everyone, I have the problem that kdevelop won't compile with gcc3.3.5: grep: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la: No such file or directory /bin/sed: can't read /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la: No such file or directory libtool: link: `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la' is not avalid libtool archive make[3]: *** [libartskde.la] Fehler 1 make[3]: Leaving directory `/var/tmp/portage/kdelibs-3.3.2-r2/work/kdelibs-3.3.2/arts/kde' Any hints on this? I guess downgrading to gcc 3.3.4 would help, but keeping 3.3.5 would be nice. Thanks in advance Rainer Sinsch |
| |||
| On Wed, 02 Feb 2005 19:16:23 +0000, Rainer Sinsch wrote: > Hello everyone, > > I have the problem that kdevelop won't compile with gcc3.3.5: > > grep: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la: No such file or > directory > /bin/sed: can't read /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la: > No such file or directory > libtool: link: `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la' is > not avalid libtool archive > make[3]: *** [libartskde.la] Fehler 1 > make[3]: Leaving directory > `/var/tmp/portage/kdelibs-3.3.2-r2/work/kdelibs-3.3.2/arts/kde' > > Any hints on this? I guess downgrading to gcc 3.3.4 would help, but keeping > 3.3.5 would be nice. > I'm no guru, but check your gcc-config settings and revdep-rebuild - probably it will recompile it properly |
| |||
| On Wed, 02 Feb 2005 19:16:23 +0000, Rainer Sinsch wrote: > Any hints on this? I guess downgrading to gcc 3.3.4 would help, but keeping > 3.3.5 would be nice. fix_libtool_files.sh 'gcc -dumpversion' -- Professor: I've been a Harold Zoid fan since back when my hips were made of bone. |
| |||
| Rainer Sinsch wrote: > I have the problem that kdevelop won't compile with gcc3.3.5: > > grep: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la: No such > file or directory > /bin/sed: can't read /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la: > No such file or directory > libtool: link: `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.la' is > not avalid libtool archive > make[3]: *** [libartskde.la] Fehler 1 > make[3]: Leaving directory > `/var/tmp/portage/kdelibs-3.3.2-r2/work/kdelibs-3.3.2/arts/kde' > > Any hints on this? I guess downgrading to gcc 3.3.4 would help, but > keeping 3.3.5 would be nice. Ancient problem that I'm surprised you haven't run into before now. Just run '/sbin/fix_libtool_files.sh 3.3.4'. The ebuild for gcc 3.3.5 should have done it, but apparently there was a glitch. -- PeKaJe A woman can look both moral and exciting -- if she also looks as if it were quite a struggle. -- Edna Ferber |
| |||
| This helped. Thank you very much for the ultra fast support! Anyway, shouldn't emerge do this automatically? /rainer Geoff King wrote: > On Wed, 02 Feb 2005 19:16:23 +0000, Rainer Sinsch wrote: > >> Any hints on this? I guess downgrading to gcc 3.3.4 would help, but >> keeping 3.3.5 would be nice. > > fix_libtool_files.sh 'gcc -dumpversion' > |
| |||
| > I'm no guru, but check your gcc-config settings and revdep-rebuild - > probably it will recompile it properly Thanks for the tip! I also had this with installing the latest gcc this morning. I don't know if this is possible, but apparently something moved from /usr/lib/gcc/i686-pc-linux-gnu/3.4.3/ to /usr/lib/gcc/i686-pc-linux-gnu/3.4.4, begin libstdc++.so.6.0.3 and the links to libstdc++.so.6 and libstdc++.son so I had to put em there manually This broke a lot of stuff, KDE would not work anymore because it was complaining about a lissing libstdc++.so.6, but that revdep-rebuild thing did the trick (maybe I'm forgetting something here, but I tried many things, so :-) Does any of you peole know btw what to do when Font Installer in the ControlCenter is complaining about missing symbols? /usr/kde/3.3/lib/libkfontinst.so.0 -> Missing symbol: FTC_SBit_Cache_Lookup, and the cause is either that I have old third party modules lying arround (can you get rid of those?) or because of an orphaned control module during KDE upgrade. Is there anything to fix that? Regards, Wimmy |
| ||||
| On Wed, 02 Feb 2005 20:35:17 +0000, Rainer Sinsch wrote: > Anyway, shouldn't emerge do this automatically? Yes, the ebuild for that version of gcc was buggy. -- BOFH Excuse #312: incompatible bit-registration operators |