| View previous topic :: View next topic |
| Author |
Message |
Schoko
n00b
Joined: 27 Jun 2002
Posts: 39
Location: Currently anywhere in Europe...
|
 Posted: Sat Mar 05, 2005 4:15 pm Post subject: The "famous" libstdc++.la problem |
 |
|
Hi Gentoo fans,
during emerging kdelibs, the "famous" error occurs:
| Code: | grep: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.4.3-20050110/libstdc++.la: No such file or directory
/bin/sed: can't read /usr/lib/gcc-lib/i686-pc-linux-gnu/3.4.3-20050110/libstdc++.la: No such file or directory
libtool: link: `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.4.3-20050110/libstdc++.la' is not avalid libtool archive
make[3]: *** [libkio.la] Fehler 1
|
I searched the whole Gentoo forums for this error, and I tried almost everything suggested there (including re-emerging gcc and libtool, revdep-rebuild and fix_libtool_files.sh, and yes, I didn't forgot env-update and source /etc/profile) - but nothing worked. The error seems a little bit strange, because gcc-3.4.3-20050110 is not an old, but my current gcc version. 
Here's my emerge --info:
| Code: |
Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.4.3-20050110, glibc-2.3.4.20050125-r0, 2.6.10-gentoo-r7 i686)
=================================================================
System uname: 2.6.10-gentoo-r7 i686 Intel(R) Pentium(R) 4 CPU 2.00GHz
Gentoo Base System version 1.6.9
Python: dev-lang/python-2.3.5 [2.3.5 (#1, Feb 23 2005, 17:01:20)]
dev-lang/python: 2.3.5
sys-devel/autoconf: 2.59-r6, 2.13
sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5
sys-devel/binutils: 2.15.92.0.2-r4
sys-devel/libtool: 1.5.10-r5
virtual/os-headers: 2.6.8.1-r2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=pentium4 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=pentium4 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="http://ftp.uni-erlangen.de/pub/mirrors/gentoo"
LANG="de_DE@euro"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="x86 X aalib acpi aim alsa apache2 apm arts avi bitmap-fonts cdr crypt cups curl dgadivx4linux dvd dvdr emboss encode esd exif f77 fam fbcon flac font-server foomaticdb fortran gdbm gif gpm icq imagemagick imlib ipv6 jabber jpeg kde libg++ libwww mad mikmod mmxmng motif mpeg mysql ncurses nls nptl oggvorbis opengl oscar oss pam pda pdf pdflib perlpng pnp ppds python qt quicktime readline samba scanner sdl sse ssl svg svga tcpd tiff truetype truetype-fonts type1-fonts unicode usb wmf xine xinerama xml2 xv xvid zlib"
Unset: ASFLAGS, CBUILD, CTARGET, LC_ALL, LDFLAGS
|
Any ideas? I'm really frustrated because nothing worked. 
Thank you very much for your help.
Juergen |
|
| Back to top |
|
 |
firephoto
Veteran
Joined: 29 Oct 2003
Posts: 1612
Location: +48° 5' 23.40", -119° 48' 30.00"
|
| Posted: Sat Mar 05, 2005 6:08 pm Post subject: |
|
|
You did a:
fix_libtool_files.sh 3.4.3
??
It's not always for older versions, usually whatever version it complains is broke. |
|
| Back to top |
|
|
Schoko
n00b
Joined: 27 Jun 2002
Posts: 39
Location: Currently anywhere in Europe...
|
| Posted: Sat Mar 05, 2005 6:35 pm Post subject: |
|
|
Yes, I did fix_libtool_files with almost every version (even 3.3.4), but the only version fix_libtool_files fixed anything was with version 3.4.3. By the way, these gcc versions are installed on my system:
| Code: | [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 |
The version before 3.4.3-20050110 was 3.4.3-r1, I guess. Should I try a downgrade of gcc? There are different opinions about that in this forums. Or should I switch to 3.3.4? |
|
| Back to top |
|
|
Halcy0n
Developer
Joined: 17 Sep 2003
Posts: 1682
Location: Freehold, NJ
|
| Posted: Sat Mar 05, 2005 6:40 pm Post subject: |
|
|
| Code: | | fix_libtool_files.sh 3.4.3-20050110 |
Try that.
_________________
Mark Loeser
http://www.halcy0n.com |
|
| Back to top |
|
|
Schoko
n00b
Joined: 27 Jun 2002
Posts: 39
Location: Currently anywhere in Europe...
|
| Posted: Sat Mar 05, 2005 7:00 pm Post subject: |
|
|
I did already, but the script did only:
| Quote: | # fix_libtool_files.sh 3.4.3-20050110
* Scanning libtool files for hardcoded gcc library paths... |
(and nothing more!), instead of:
| Quote: | # fix_libtool_files.sh 3.3.4
* Scanning libtool files for hardcoded gcc library paths...
* [1/6] Scanning /lib ...
* [2/6] Scanning /usr/lib ...
* [3/6] Scanning /usr/i686-pc-linux-gnu/lib ...
* [4/6] Scanning /usr/kde/3.3/lib ...
* [5/6] Scanning /usr/local/lib ...
* [6/6] Scanning /usr/qt/3/lib ... |
When I run "fix_libtool_files.sh 3.4.3", a lot of kde libraries are fixed on the 4th step.
Very strange... |
|
| Back to top |
|
|
Halcy0n
Developer
Joined: 17 Sep 2003
Posts: 1682
Location: Freehold, NJ
|
| Posted: Sat Mar 05, 2005 7:20 pm Post subject: |
|
|
| Schoko wrote: | I did already, but the script did only:
| Quote: | # fix_libtool_files.sh 3.4.3-20050110
* Scanning libtool files for hardcoded gcc library paths... |
(and nothing more!) |
You sure you gave it enough time? Executes fine for me.
_________________
Mark Loeser
http://www.halcy0n.com |
|
| Back to top |
|
|
Schoko
n00b
Joined: 27 Jun 2002
Posts: 39
Location: Currently anywhere in Europe...
|
| Posted: Sat Mar 05, 2005 7:31 pm Post subject: |
|
|
How much time should I give - and how?
I entered the command in the console window (or plain shell, no difference), the message "Scanning..." appears, the harddisk starts to rumble, the harddisk stops to rumble, and the console prompt is shown again... 
Seems that this happy little script is doing harakiri... *hrgh* |
|
| Back to top |
|
|
Schoko
n00b
Joined: 27 Jun 2002
Posts: 39
Location: Currently anywhere in Europe...
|
| Posted: Sun Mar 06, 2005 11:08 am Post subject: |
|
|
Frustration continous...
I downgraded to GCC-3.4.3-r1 again, ran the whole good things (fix_libtool_files, env-update etc.) again, but nothing changed. Compilation stops because "libstdc++.la' is not avalid libtool archive".
One thing about the fix_libtool_files.sh script: When the first parameter is the same as the installed GCC version, the scripts stops without any scanning (for me now with "3.4.3" instead of "3.4.3-20050110"). This seems to be designedly.
Does anybody have ANY suggestions? |
|
| Back to top |
|
|
Cintra
Advocate
Joined: 03 Apr 2004
Posts: 2111
Location: Norway
|
| Posted: Sun Mar 06, 2005 11:33 am Post subject: |
|
|
emerge glibc binutils gcc && glibc binutils gcc for a start
your ACCEPT_KEYWORDS="x86 ~x86" seems a bit odd to me..?
mvh
_________________
"I am not bound to please thee with my answers" W.S. |
|
| Back to top |
|
|
acidlog
n00b
Joined: 13 Oct 2004
Posts: 45
Location: Germany
|
| Posted: Sun Mar 06, 2005 2:06 pm Post subject: |
|
|
i have a question:
i would emerge kdemultimedia 3.3.2 but i got a link error. the error say the typical problem dont found the file.
my problem was i unmerged the gcc 3.4.0 and the link was searched in the | Quote: | | /usr/lib/gcc-lib/i686-pc-linux-gnu/3.4.3/ |
folder.
the problem is this folder dont existing anymore. (unmerge)
thats my
| Quote: | gcc-config -l
[1] i686-pc-linux-gnu-3.3.4
[2] i686-pc-linux-gnu-3.3.5
[3] i686-pc-linux-gnu-3.3.5-hardened
[4] i686-pc-linux-gnu-3.3.5-hardenednopie
[5] i686-pc-linux-gnu-3.3.5-hardenednossp |
the solution is i emerge again gcc-3.4.3. i have used the fix_libtool_files.sh but and i emerge gcc 3.4.3 again but i get always the link error.
why he would like link to | Quote: | | /usr/lib/gcc-lib/i686-pc-linux-gnu/3.4.3/ |
this path and how or where teh gcc save the information about this link???? there is not 3.4.3 directory.
how i can fix this problem? |
|
| Back to top |
|
|
Schoko
n00b
Joined: 27 Jun 2002
Posts: 39
Location: Currently anywhere in Europe...
|
| Posted: Sun Mar 06, 2005 5:46 pm Post subject: |
|
|
@Cintra:
I emerged glibc, binutils, gcc and libtools (the latest versions) again (and again)... but it doesn't help.
@acidlog:
I found the libstdc++.la in the /usr/lib/gcc/i686-pc-linux-gnu/3.4.3-20050110 directory. Yes, in /usr/lib/gcc, not /usr/lib/gcc-lib. Now I made a symlink from /usr/lib/gcc/i686-pc-linux-gnu/3.4.3-20050110 to /usr/lib/gcc-lib/i686-pc-linux-gnu/. This is not a perfect solution, and I don't know yet if it works. kdelibs is compiling right now, if it fails or succeeds I'll post it here... |
|
| Back to top |
|
|
firephoto
Veteran
Joined: 29 Oct 2003
Posts: 1612
Location: +48° 5' 23.40", -119° 48' 30.00"
|
| Posted: Sun Mar 06, 2005 6:34 pm Post subject: |
|
|
| Have either of you ran gcc-config and set your gcc version (not just looked at what was set). Acidlog your gcc-config -l seems to show you don't have a version selected so you should run "gcc-config 2". |
|
| Back to top |
|
|
acidlog
n00b
Joined: 13 Oct 2004
Posts: 45
Location: Germany
|
| Posted: Sun Mar 06, 2005 6:59 pm Post subject: |
|
|
| sorry firephoto i forgot 3.3.5 is set as standard compiler. |
|
| Back to top |
|
|
Schoko
n00b
Joined: 27 Jun 2002
Posts: 39
Location: Currently anywhere in Europe...
|
| Posted: Sun Mar 06, 2005 7:25 pm Post subject: |
|
|
Yippie! kdelibs compiled now, thanks to the symlink. So if anybody has the same error and tried everything else before (re-emerging gcc glibc binutils, fix_libtool_files, revdep_rebuild, etc.), so try this:
| Code: | | ln -s /usr/lib/gcc/i686-pc-linux-gnu/3.4.3-20050110 /usr/lib/gcc-lib/i686-pc-linux-gnu/ |
That maybe helps.
The big question for me is now, what happens if the symlink is removed (manual or be emerging gcc again). Any ideas? |
|
| Back to top |
|
|
acidlog
n00b
Joined: 13 Oct 2004
Posts: 45
Location: Germany
|
| Posted: Sun Mar 06, 2005 7:48 pm Post subject: |
|
|
yes i set a link from
| Quote: | | ln -s /usr/lib/gcc/i686-pc-linux-gnu/3.4.3 /usr/lib/gcc-lib/i686-pc-linux-gnu/ |
i dont have an idea i have only unmerge gcc-3.4.0 because i would only stable packages. i thought i dont need it.
i could compile kdemultimedia with success. no problems but WHY need kdemultimedia 3.3.2 the gcc 3.4.0? |
|
| Back to top |
|
|
LordArthas
Guru
Joined: 01 Nov 2004
Posts: 500
Location: Maniago, Friûl, Italia
|
| Posted: Tue Mar 22, 2005 3:52 pm Post subject: |
|
|
Hi Schoko!
I has the same problem while upgrading kdelibs to versione 3.3.2-r7. Like you I had to:
| Code: |
ln -s /usr/lib/gcc/i686-pc-linux-gnu/3.4.3-20050110 /usr/lib/gcc-lib/i686-pc-linux-gnu/
|
and then everything worked fine!
Thanks!
Michele. |
|
| Back to top |
|
|
gour
Apprentice
Joined: 16 Apr 2003
Posts: 231
Location: Zagreb, Croatia
|
| Posted: Tue Mar 22, 2005 6:22 pm Post subject: |
|
|
Hi!
| Schoko wrote: | Yippie! kdelibs compiled now, thanks to the symlink. So if anybody has the same error and tried everything else before (re-emerging gcc glibc binutils, fix_libtool_files, revdep_rebuild, etc.), so try this:
| Code: | | ln -s /usr/lib/gcc/i686-pc-linux-gnu/3.4.3-20050110 /usr/lib/gcc-lib/i686-pc-linux-gnu/ |
That maybe helps. |
I have some problems with Quanta crashing and went to upgrade gcc, glibc, binutils...and hit the same problem but thanks to you the symlink (albeit a little bit different) solved it 
I am on amd64 and had to make a symlink:
| Code: | | ln -s /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3 /usr/lib/gcc-lib/x86_64-pc-linux-gnu/3.4.3 |
| Quote: | | The big question for me is now, what happens if the symlink is removed (manual or be emerging gcc again). Any ideas? |
Have you tried to remove symlink?
Maybe we should submit a bug report for this gcc-issues 
Sincerely,
Gour |
|
| Back to top |
|
|
feardapenguin
Guru
Joined: 23 Jul 2003
Posts: 414
Location: Texas
|
| Posted: Tue Mar 29, 2005 1:51 am Post subject: |
|
|
Same problem with kdelibs here.
I don't see how the symlink solution can work. In my case /usr/lib/gcc is set as a symlink to /usr/lib/gcc-lib, so /usr/lib/gcc-lib/i686-pc-linux-gnu/ already exists.
| Code: | [/usr/lib]# ll -d gcc*
lrwxrwxrwx 1 root root 7 Dec 5 21:06 gcc -> gcc-lib
drwxr-xr-x 3 root root 88 Dec 5 12:20 gcc-lib |
|
|
| Back to top |
|
|
firephoto
Veteran
Joined: 29 Oct 2003
Posts: 1612
Location: +48° 5' 23.40", -119° 48' 30.00"
|
| Posted: Tue Mar 29, 2005 2:44 am Post subject: |
|
|
| I don't think there's any reason to do any symlinking.. The fix_libtools and gcc-config should be all that's needed. If you symlink something chances are it will be broke next time you upgrade gcc or whatever it is that's breaking your symlinks. Use the system tools, that's why they're there. |
|
| Back to top |
|
|
feardapenguin
Guru
Joined: 23 Jul 2003
Posts: 414
Location: Texas
|
| Posted: Tue Mar 29, 2005 4:15 am Post subject: |
|
|
In this case the system tool accomplishes nothing.
| Code: | [22:10:06][~]# fix_libtool_files.sh 3.4.3-20050110
* Scanning libtool files for hardcoded gcc library paths...
[22:10:07][~]# |
| Code: | [~]# 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
[~]# gcc-config 2
* Switching to i686-pc-linux-gnu-3.4.3-20050110 compiler ...
[~]# |
I still get the same error when compiling kdelibs.
| Code: | <snip>
/bin/sh ../../libtool --silent --mode=link --tag=CXX i686-pc-linux-gnu-g++ -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -march=i686 -O3 -pipe -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -fno-exceptions -fno-check-new -fno-common -fvisibility=hidden -fvisibility-inlines-hidden -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -o libartskde.la -rpath /usr/kde/3.4/lib -L/usr/kde/3.4/lib -L/usr/qt/3/lib -L/usr/lib -no-undefined -Wl,--no-undefined -Wl,--allow-shlib-undefined -version-info 3:0:2 artskde.lo kioinputstream_impl.lo kplayobject.lo kplayobjectfactory.lo kartsfloatwatch.lo kartsdispatcher.lo kaudiorecordstream.lo kaudioplaystream.lo kartsserver.lo kdatarequest_impl.lo kaudioconverter.lo kvideowidget.lo kplayobjectcreator.lo kaudiomanagerplay.lo ../../kio/libkio.la -lqtmcop -lsoundserver_idl
grep: //usr/lib/gcc/i686-pc-linux-gnu/3.4.3/libstdc++.la: No such file or directory
/bin/sed: can't read //usr/lib/gcc/i686-pc-linux-gnu/3.4.3/libstdc++.la: No such file or directory
libtool: link: `//usr/lib/gcc/i686-pc-linux-gnu/3.4.3/libstdc++.la' is not a valid libtool archive
make[3]: *** [libartskde.la] Error 1
make[3]: Leaving directory `/var/tmp/portage/kdelibs-3.4.0/work/kdelibs-3.4.0/arts/kde'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/kdelibs-3.4.0/work/kdelibs-3.4.0/arts'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/kdelibs-3.4.0/work/kdelibs-3.4.0'
make: *** [all] Error 2
!!! ERROR: kde-base/kdelibs-3.4.0 failed.
!!! Function kde_src_compile, Line 166, Exitcode 2
!!! died running emake, kde_src_compile:make
!!! If you need support, post the topmost build error, NOT this status message. |
Note that the path it is looking for is "/usr/lib/gcc/i686-pc-linux-gnu/3.4.3", not "/usr/lib/gcc/i686-pc-linux-gnu/3.4.3-20050110".
Something is still hard-coded. I could symlink 3.4.3 to 3.4.3-20050110 but I agree that symlinking is a sloppy solution.
Last edited by feardapenguin on Tue Mar 29, 2005 4:25 am; edited 1 time in total |
|
| Back to top |
|
|
firephoto
Veteran
Joined: 29 Oct 2003
Posts: 1612
Location: +48° 5' 23.40", -119° 48' 30.00"
|
| Posted: Tue Mar 29, 2005 4:24 am Post subject: |
|
|
Yes, probably a symlink made by hand.  |
|
| Back to top |
|
|
feardapenguin
Guru
Joined: 23 Jul 2003
Posts: 414
Location: Texas
|
| Posted: Tue Mar 29, 2005 4:30 am Post subject: |
|
|
| Do you mean I've symlinked something previously that is hosing me now? I don't think so. I usually avoid 'quick-and-dirty' fixes when possible. |
|
| Back to top |
|
|
firephoto
Veteran
Joined: 29 Oct 2003
Posts: 1612
Location: +48° 5' 23.40", -119° 48' 30.00"
|
| Posted: Tue Mar 29, 2005 5:05 am Post subject: |
|
|
| feardapenguin wrote: | In this case the system tool accomplishes nothing.
| Code: | [22:10:06][~]# fix_libtool_files.sh 3.4.3-20050110
* Scanning libtool files for hardcoded gcc library paths...
[22:10:07][~]# |
|
Did you try "fix_libtool_files.sh 3.4.3" since that's the one it's looking for? From the looks of your error that should fix you up. |
|
| Back to top |
|
|
gour
Apprentice
Joined: 16 Apr 2003
Posts: 231
Location: Zagreb, Croatia
|
| Posted: Tue Mar 29, 2005 7:53 am Post subject: |
|
|
| firephoto wrote: | | I don't think there's any reason to do any symlinking.. The fix_libtools and gcc-config should be all that's needed. If you symlink something chances are it will be broke next time you upgrade gcc or whatever it is that's breaking your symlinks. Use the system tools, that's why they're there. |
This is a good piece of advice
After I did a symlink and finished my 'emerge -ue world', I removed created symlink and kdelibs emerged without a problem
Pls. don't ask me why the symlink was required as an 'interim' solution
Sincerely,
Gour |
|
| Back to top |
|
|
feardapenguin
Guru
Joined: 23 Jul 2003
Posts: 414
Location: Texas
|
| Posted: Wed Mar 30, 2005 1:40 am Post subject: |
|
|
| firephoto wrote: | | Did you try "fix_libtool_files.sh 3.4.3" since that's the one it's looking for? From the looks of your error that should fix you up. |
That did the trick.
Thnx |
|
| Back to top |
|
|
|
Portage & Programming
