Summary: | Cannot link/find libstdc++ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Seth Chandler <sethbc> |
Component: | New packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alain, alexander, azarah, caleb, clint, hsggebhardt, liviu.voicu, lv, qubex, smys, throstur |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Seth Chandler
2003-02-03 05:28:20 UTC
*** Bug 15027 has been marked as a duplicate of this bug. *** Ok, to fix: nosferatu root # emerge rsync nosferatu root # cd /usr/portage/sys-devel/gcc/files/ nosferatu files # ./fix_libtool_files.sh 3.2.1 * Scanning /usr/lib/opengl/nvidia/lib... * Scanning /usr/lib/mozilla... * Scanning /usr/X11R6/lib... * Scanning /opt/blackdown-jdk-1.4.1_beta/jre/lib/i386... * Scanning /opt/blackdown-jdk-1.4.1_beta/jre/lib/i386/native_threads... * Scanning /usr/qt/3/lib... * Scanning /lib... * Scanning /usr/lib... * FIXING: /usr/lib/gst/libgstarts.la * Scanning /usr/local/lib... nosferatu files # Make sure that /usr/portage/sys-devel/gcc/files/awk/fixlafiles.awk is at CVS revision 1.5: ------------------------------------------------------- azarah@nosferatu awk $ grep fixlafiles /usr/portage/sys-devel/gcc/files/awk/fixlafiles.awk # $Header: /home/cvsroot/gentoo-x86/sys-devel/gcc/files/awk/fixlafiles.awk,v 1.5 2003/02/03 18:35:40 azarah Exp $ azarah@nosferatu awk $ ------------------------------------------------------- Note the 'v 1.5' ... thanks, good job gentoo team, bcoz of this people like gentoo :-) Err, that is a confirmation that the fix work ? It worked for me, had the same error in kdelibs. I had the same error with many programs....the script seems to work, but I noticed the same thing on my other boxes, the script error/doesn't run correctly from the gcc3.2.2 ebuild. Stupid me then tried running the script manually, but used 3.2.2 as an argument which didn't fix the problem, so I ended up grepping for 3.2.1/libstdc++.la and recompiling each package :) until I see that u need the old version as an argument which works great. I still wish I knew whats up with the line wrapping now AFAICS this is fixed, reopen if I'm wrong. *** Bug 15066 has been marked as a duplicate of this bug. *** *** Bug 14350 has been marked as a duplicate of this bug. *** *** Bug 15288 has been marked as a duplicate of this bug. *** I guess my bug #14350 has been marked as a dupe of this bug, but the fix for this bug did not fix my problem. I want to make clear that when my gcc is built, there is no libstdc++.so.5, libstdc++.so.5.2, or libstdc++.so in /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2. ls -al /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/libstdc++* -rw-r--r-- 1 root root 7932070 Mar 13 16:47 /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/libstdc++.a -rwxr-xr-x 1 root root 909 Mar 13 16:47 /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.2/libstdc++.la That's all I got. I was told to run this script before, and it did seem to fix some things up, but the only reason I still have a working system is that some binary gcc I downloaded kept some files in /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/ and that's still in my path, so python will work, but anything that tries to use that file will die with the time_put_w error. I don't think I have the same problem as these folks. Also, a weird thing, when I run gcc-config i686-pc-linux-gnu-3.2.2 i get /bin/cp: cannot stat `/usr/lib/gcc-config/wrapper': No such file or directory over and over and it ends with [ ok ]. Something maybe wrong with gcc-config? Clint: Check that bug for your answer ... *** Bug 20125 has been marked as a duplicate of this bug. *** *** Bug 18041 has been marked as a duplicate of this bug. *** *** Bug 19879 has been marked as a duplicate of this bug. *** *** Bug 19896 has been marked as a duplicate of this bug. *** I just installed a new and shiny Gentoo system a couple of weeks ago :-). I have the same problem upgrading from gcc-3.2.3 to gcc-3.3.2. I don't know if the fix in this report works. I just followed bug number 11391 before I found this one, then re-emerged python, and finally deleted the copied files (see bug 11391). Emerge is working again, now. This bug just seems be sticking around! Same problem here upgrading gcc. Fixed by replacing /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3 with /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2 in /e tc/ld.so.conf Is anyone working on fixing this? Did you run fix_libtool_files.sh? Question: Do you need to run fix_libtool_files.sh everytime you upgrade gcc? I mean, it is quite a shock to a gentoo-newcomer when emerge doesn't work anymore... |