Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 86693 - fix_libtool_files.sh 3.3.4 does not work after updating gcc to 3.4.3
Summary: fix_libtool_files.sh 3.3.4 does not work after updating gcc to 3.4.3
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-25 12:00 UTC by jakie jia
Modified: 2005-03-27 06:56 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jakie jia 2005-03-25 12:00:41 UTC
just updated gcc to 3.4.3 from 3.3.4
and called "fix_libtool_files.sh 3.3.4"

but still getting error when emergin php:
grep: /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.4/libstdc++.la: No such file or directory
/bin/sed: can't read /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.4/libstdc++.la: No such file or directory
libtool: link: `/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.4/libstdc++.la' is not a valid libtool archive


Reproducible: Always
Steps to Reproduce:
1.emerge php
2.
3.

Actual Results:  
grep: /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.4/libstdc++.la: No such file or 
directory
/bin/sed: can't read /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.4/libstdc++.la: No 
such file or directory
libtool: link: `/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.4/libstdc++.la' is not 
a valid libtool archive
make: *** [libphp5.la] Error 1
make: *** Waiting for unfinished jobs....
libtool: link: cannot find the library `/usr/lib/gcc-lib/i386-pc-linux-
gnu/3.3.4/libstdc++.la'
make: *** [sapi/cli/php] Error 1



i've tried re-emerge libtool, fix_libtool_files. 3.3.4

emerge php still fails.
Comment 1 jakie jia 2005-03-25 12:28:59 UTC
fixed by adding --oldarch i386-pc-linux-gnu

humm... i never used such arch....
anyway, sorry for the trouble.
Comment 2 Guillaume Castagnino 2005-03-27 06:56:50 UTC
Same problem here fixed with a very bad againt /lib/rcscripts/awk/fixlafiles.awk that force HAVE_GCC34 = 1 and disabling some checks to run fix_libtool_files.sh against same gcc version :

===============8<================
--- /lib/rcscripts/awk/fixlafiles.awk   2005-03-21 09:45:40.000000000 +0100
+++ fixlafiles.awk      2005-03-27 16:51:41.000000000 +0200
@@ -155,4 +155,6 @@
        GCCLIBPREFIX_OLD = "/usr/lib/gcc-lib/"
        GCCLIBPREFIX_NEW = "/usr/lib/gcc/"
+
+    HAVE_GCC34 = 1
 
        if (HAVE_GCC34)
@@ -179,6 +181,6 @@
 
        # Nothing to do ?
-       if ((OLDVER == NEWVER) && (OLDCHOST == ""))
-               exit 0
+       ###if ((OLDVER == NEWVER) && (OLDCHOST == ""))
+       ###     exit 0
 
        #
@@ -215,5 +217,5 @@
                                        }
                                }
-                               if (OLDVER != NEWVER) {
+                               ###if (OLDVER != NEWVER) {
                                        if ((gsub(GCCLIBPREFIX_OLD CHOST "/" OLDVER "[/[:space:]]*",
                                                  GCCLIB "/" NEWVER, la_data) > 0) ||
@@ -221,5 +223,5 @@
                                                  GCCLIB "/" NEWVER, la_data) > 0))
                                                CHANGED = 1
-                               }
+                               ###}
                        }
                        close(la_files)
@@ -269,5 +271,5 @@
                                        }
 
-                                       if (OLDVER != NEWVER) {
+                                       ###if (OLDVER != NEWVER) {
                                                # Catch:
                                                #
@@ -292,5 +294,5 @@
                                                        la_data = tmpstr
                                                }
-                                       }
+                                       ###}
 
                                        print la_data >> (la_files ".new")
===============>8================

I know it's a VERY BAD patch, but runing fix_libtool_files.sh after applying this patch solve the problem for me.
It seems that gcc 3.4.3-20050110 is not recognized as a gcc 3.4 version but lower, so the library path used is "/usr/lib/gcc-lib/" instead of "/usr/lib/gcc/" that make the mess...