View previous topic :: View next topic |
Author |
Message |
Clapper Apprentice
Joined: 29 Sep 2003 Posts: 177
|
Posted: Thu Feb 26, 2004 4:16 pm Post subject: libstdc++.la: No such file or directory -- Please help! |
|
|
When emerging mod_php, I am getting the error in the subject line. I thought a recent upgrade of gcc might have messed up something, and I re-emerged it, but still the error, when building other packages, such as mod_php.
Is there a package I should re-emerge to created the missing files and directories, and prevent the errors, below?
Thanks!!!
Code: |
-I/var/tmp/portage/mod_php-4.3.4-r4/work/php-4.3.4/TSRM -O2 -mcpu=i686 -pipe -prefer-pic -c /var/tmp/portage/mod_php-4.3.4-r4/work/php-4.3.4/ext/java/java.c -o ext/java/java.lo
grep: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/libstdc++.la: No such file or directory
/bin/sed: can't read /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/libstdc++.la: No such file or directory
libtool: link: `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/libstdc++.la' is not a valid libtool archive
make: *** [libphp4.la] Error 1
make: *** Waiting for unfinished jobs....
!!! ERROR: dev-php/mod_php-4.3.4-r4 failed.
!!! Function php-sapi_src_compile, Line 450, Exitcode 2
!!! compile problem
|
|
|
Back to top |
|
|
aja l33t
Joined: 26 Aug 2002 Posts: 705 Location: Edmonton, Canada
|
Posted: Thu Feb 26, 2004 4:26 pm Post subject: |
|
|
Quite probably related to your gcc upgrade.
Try
And, perhaps, take a look at https://forums.gentoo.org/viewtopic.php?t=134400
You might also consider re-merging glibc, but that takes a while, and I am not certain would resolve your issue. |
|
Back to top |
|
|
Clapper Apprentice
Joined: 29 Sep 2003 Posts: 177
|
Posted: Thu Feb 26, 2004 10:03 pm Post subject: |
|
|
Arg. No help.
I re-emerged glibc, ran ldconfig, and env-update to no avail.
In fact, I don't have the directory in question:
Code: |
server init.d # ls -la /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3
ls: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3: No such file or directory
|
I do have this directory:
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2
Why would emerge, or, libtool be trying to use the other directory referred to in the error message:
Code: |
-I/var/tmp/portage/mod_php-4.3.4-r4/work/php-4.3.4/TSRM -O2 -mcpu=i686 -pipe -prefer-pic -c /var/tmp/portage/mod_php-4.3.4-r4/work/php-4.3.4/ext/java/java.c -o ext/java/java.lo
grep: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/libstdc++.la: No such file or directory
/bin/sed: can't read /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/libstdc++.la: No such file or directory
libtool: link: `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.3/libstdc++.la' is not a valid libtool archive
make: *** [libphp4.la] Error 1
make: *** Waiting for unfinished jobs....
!!! ERROR: dev-php/mod_php-4.3.4-r4 failed.
!!! Function php-sapi_src_compile, Line 450, Exitcode 2
!!! compile problem
|
any other suggestions?
Thanks very much |
|
Back to top |
|
|
Clapper Apprentice
Joined: 29 Sep 2003 Posts: 177
|
Posted: Thu Feb 26, 2004 10:08 pm Post subject: |
|
|
PS:
I also tried this, which would seem to be a fix related to my previous observations:
Code: |
Thanks to all.
I had to fix .../3.2.3 and .../3.2 refs to.../3.3.2 and .../3.3
in files:
/etc/ld.so.conf and /etc/env.d/05gcc
then run:
ldconfig; etc-update; env-update
then all ok again
|
Unfortunately, no help for me! I wonder why the errors in my
emerge are referring to 3.2.3 and not 3.3.2????
Thanks for any comments.... |
|
Back to top |
|
|
Clapper Apprentice
Joined: 29 Sep 2003 Posts: 177
|
Posted: Fri Feb 27, 2004 12:19 am Post subject: |
|
|
Ok, someone said I should run ldconfig -v | grep gcc and check the output.
Here is what I get:
Code: |
ldconfig -v | grep gcc
ldconfig: Can't stat /opt/blackdown-jdk-1.4.1/jre/lib/i386/classic: No such file or directory
ldconfig: Path `/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2' given more than once
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2:
libgcc_s.so.1 -> libgcc_s.so.1
|
Sorry to be such a noob (see my icon for clarification), but, what is this telling me? Is it related to my problem? How can I correct? |
|
Back to top |
|
|
jammib n00b
Joined: 06 May 2003 Posts: 35 Location: UK
|
|
Back to top |
|
|
Clapper Apprentice
Joined: 29 Sep 2003 Posts: 177
|
Posted: Fri Feb 27, 2004 7:22 pm Post subject: |
|
|
Thanks jammib!
I had, as a workaround, created a soft link pointing to the correct file in the 3.3.2 directory.
I think the suggestions in your link may fix the root of the problem, however.
Clapper |
|
Back to top |
|
|
chaoslord007 n00b
Joined: 26 Aug 2003 Posts: 14 Location: Wernersberg - Germany
|
Posted: Thu Mar 04, 2004 7:59 pm Post subject: |
|
|
Only the Symlink workaround solved this problem at my AthlonXP/2000+/512MB/2.6.3-r3Kernel/gcc 3.3.2
a gcc 3.2.3 never existet on this system !
tried this and severeal other forum thread instructions, no help.
there must be an other way, I hope ;-)
so long, all seems to work ok with the symlink _________________ Immer Dusma bleiwe |
|
Back to top |
|
|
nagini n00b
Joined: 20 Mar 2003 Posts: 5 Location: Los Angeles, CA USA
|
Posted: Fri Mar 12, 2004 12:44 am Post subject: |
|
|
The right way to fix this seemingly unfixable problem is to run
Code: | fix_libtool_files.sh 3.2.3 |
The problem is that the .la libraries on you system have hard references to the old gcc libs. The symlink trick works but this is a more 'satisfying' solution. |
|
Back to top |
|
|
kodos n00b
Joined: 29 Sep 2002 Posts: 20
|
Posted: Tue Mar 16, 2004 3:45 pm Post subject: |
|
|
nagini, thanks for the tip, it worked like a charm. This one's had me scratching my head for quite some time. |
|
Back to top |
|
|
cayenne l33t
Joined: 17 Oct 2002 Posts: 945 Location: New Orleans
|
Posted: Tue Mar 30, 2004 2:26 am Post subject: Worked!! |
|
|
nagini wrote: | The right way to fix this seemingly unfixable problem is to run
Code: | fix_libtool_files.sh 3.2.3 |
The problem is that the .la libraries on you system have hard references to the old gcc libs. The symlink trick works but this is a more 'satisfying' solution. |
This worked for me, but, what exactly does this tool do? Never had heard of it before this....
TIA,
cayenne _________________ Light travels faster than sound. This is why some people appear bright until you hear them speak......... |
|
Back to top |
|
|
tristure Apprentice
Joined: 30 Oct 2003 Posts: 270 Location: France
|
Posted: Sat Apr 03, 2004 9:51 am Post subject: |
|
|
Strange ; I tried the proposed fix, I even created a soft link and still the emerge doesn't work and returns the same error always.
I can't figure out what's going on.
Any ideas?
Or any other interesting development packages I could emerge since kdevelop won't work??
Thanks. |
|
Back to top |
|
|
langthang Retired Dev
Joined: 27 Nov 2003 Posts: 620
|
Posted: Tue Jun 01, 2004 6:57 pm Post subject: |
|
|
oops. wrong thread _________________ Gentoo users' map |
|
Back to top |
|
|
gbu n00b
Joined: 18 May 2004 Posts: 25 Location: Between UCI and UCLA
|
Posted: Wed Jun 02, 2004 12:01 am Post subject: |
|
|
I had this problem, I think. I had downgraded to gcc-3.3.2 from gcc-3.3.3.
The way I fixed it was to symlink /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.3 to
the existing 3.3.2 directory (not sure that step is necessary), and then search
the system for every .la file that referenced 3.3.3. I then re-emerged
the packages those .la files had come from, in dependency order. That
cleared up the problem for me. |
|
Back to top |
|
|
eraoul n00b
Joined: 09 Jun 2004 Posts: 3
|
Posted: Wed Jun 09, 2004 7:13 am Post subject: hack? |
|
|
It seems to me that requiring the user to run something called "fix_libtool_files.sh" is a hack. It solves the problem, but I am suprised this still isn't fixed somehow; can this not be integrated into the emerge process?? There are quite a few posts based on this issue; it seems like it's wasting lots of time!
Perhaps there's a technical reason that this can't happen automatically? If so, I would recommend adding a note about fix_libtool_files.sh to a more prominent spot; say in the portage user guide(?) so that everyone knows how to fix things when new gcc versions are released... |
|
Back to top |
|
|
M. Turunen n00b
Joined: 23 Sep 2004 Posts: 1
|
Posted: Thu Sep 23, 2004 7:09 pm Post subject: |
|
|
Old topic but I got almost same problem while emerging my world. CHOST had mysteriously changed or at least linker was searching libraries from path:
/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.3
Running this command fixed my problem:
#> fix_libtool_files.sh 3.3.3 --oldarch i386-pc-linux-gnu
3.3.3 = path after CHOST (see above)
i386-pc-linux-gnu = wrong CHOST
After this is run: ldconfig; etc-update; source /etc/profile
Not sure if above is needed but anyhow it did the trick for me
-Marko |
|
Back to top |
|
|
|