| 1 |
Csanyi Andras schreef: |
| 2 |
> Hi! |
| 3 |
|
| 4 |
Hi! |
| 5 |
> |
| 6 |
> grep: /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5-20050130/libstdc++.la: |
| 7 |
> No such file or directory /bin/sed: can't read |
| 8 |
> /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5-20050130/libstdc++.la: No |
| 9 |
> such file or directory libtool: link: |
| 10 |
> `/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5-20050130/libstdc++.la' is |
| 11 |
> not a valid libtool archive make[2]: *** [libfile.la] Error 1 |
| 12 |
> make[2]: Leaving directory |
| 13 |
> `/var/tmp/portage/gnome-vfs-2.12.1.1/work/gnome-vfs-2.12.1.1/modules' |
| 14 |
> make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory |
| 15 |
> `/var/tmp/portage/gnome-vfs-2.12.1.1/work/gnome-vfs-2.12.1.1' make: |
| 16 |
> *** [all] Error 2 |
| 17 |
> |
| 18 |
> i search the google, i find this: |
| 19 |
> http://www.usenetlinux.com/archive/topic.php/t-492900.html |
| 20 |
|
| 21 |
Right, you found something to tell you that you need to run |
| 22 |
fix_libtools_files.sh. Good! (LOL, it was me, too!). That is the the |
| 23 |
thing to do whenever you see an error containing this output: |
| 24 |
|
| 25 |
> ......libstdc++.la' is not a valid libtool archive make[2]: *** |
| 26 |
> [libfile.la] Error 1 |
| 27 |
|
| 28 |
> |
| 29 |
> and i make this: |
| 30 |
> |
| 31 |
> sayusi bundi # fix_libtool_files.sh 3.3.6 * Scanning libtool files |
| 32 |
> for hardcoded gcc library paths... |
| 33 |
|
| 34 |
This is where you wen't wrong. If you need to run the script with |
| 35 |
further parameters, the usage is: |
| 36 |
|
| 37 |
Usage: fix_libtool_files.sh <old-gcc-version> [--oldarch <old-CHOST>] |
| 38 |
|
| 39 |
(taken from reading the script with less) |
| 40 |
|
| 41 |
But the thing is, your problem is not with gcc 3.3.6, as you put in the |
| 42 |
command; if the problem is that you upgraded gcc (did you?), the proper |
| 43 |
old version of gcc is listed in the error message: |
| 44 |
|
| 45 |
3.3.5-20050130 |
| 46 |
|
| 47 |
So if libtool is failing because you upgraded gcc, the command should be |
| 48 |
|
| 49 |
fix_libtool_files.sh 3.3.5-20050130 |
| 50 |
|
| 51 |
But if libtool is failing because you changed your CHOST (with or |
| 52 |
without upgrading gcc), the command should be |
| 53 |
|
| 54 |
fix_libtool_files.sh --oldarch i386-pc-linux-gnu |
| 55 |
|
| 56 |
So you might try running the script with the correct command and see if |
| 57 |
that helps more :-) . |
| 58 |
|
| 59 |
Holly |
| 60 |
-- |
| 61 |
gentoo-user@g.o mailing list |
Archives