Re: [gentoo-user] gnome-vfs
Sat, 22 Oct 2005 14:57:40 +0200 -kor Holly Bostick [EMAIL PROTECTED] irta ezt: sayusi bundi # fix_libtool_files.sh 3.3.6 * Scanning libtool files for hardcoded gcc library paths... This is where you wen't wrong. If you need to run the script with further parameters, the usage is: Usage: fix_libtool_files.sh old-gcc-version [--oldarch old-CHOST] (taken from reading the script with less) But the thing is, your problem is not with gcc 3.3.6, as you put in the command; if the problem is that you upgraded gcc (did you?), the proper old version of gcc is listed in the error message: 3.3.5-20050130 So if libtool is failing because you upgraded gcc, the command should be fix_libtool_files.sh 3.3.5-20050130 But if libtool is failing because you changed your CHOST (with or without upgrading gcc), the command should be fix_libtool_files.sh --oldarch i386-pc-linux-gnu So you might try running the script with the correct command and see if that helps more :-) . Hi Holly! Thank you the help! My harddisk is crash, consistency problem. I make new install. have a nice day! -- -- Csanyi Andras -- -Bízzál Istenben és tartsd szárazon a puskaport. - Cromwell ...a KERNEL legyen veletek... -- gentoo-user@gentoo.org mailing list
[gentoo-user] gnome-vfs
Hi! i have a problem :) grep: /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5-20050130/libstdc++.la: No such file or directory /bin/sed: can't read /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5-20050130/libstdc++.la: No such file or directory libtool: link: `/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5-20050130/libstdc++.la' is not a valid libtool archive make[2]: *** [libfile.la] Error 1 make[2]: Leaving directory `/var/tmp/portage/gnome-vfs-2.12.1.1/work/gnome-vfs-2.12.1.1/modules' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gnome-vfs-2.12.1.1/work/gnome-vfs-2.12.1.1' make: *** [all] Error 2 i search the google, i find this: http://www.usenetlinux.com/archive/topic.php/t-492900.html and i make this: sayusi bundi # fix_libtool_files.sh 3.3.6 * Scanning libtool files for hardcoded gcc library paths... sayusi bundi # and nothing... the gnome-fvs is not compiling i reinstall the gentoo but gnome-vfs is not compiling. what do i? sorry my english and i am little nervos and tired thx! -- Csanyi Andras -- -Bízzál Istenben és tartsd szárazon a puskaport. - Cromwell ...a KERNEL legyen veletek... -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gnome-vfs
Csanyi Andras schreef: Hi! Hi! grep: /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5-20050130/libstdc++.la: No such file or directory /bin/sed: can't read /usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5-20050130/libstdc++.la: No such file or directory libtool: link: `/usr/lib/gcc-lib/i386-pc-linux-gnu/3.3.5-20050130/libstdc++.la' is not a valid libtool archive make[2]: *** [libfile.la] Error 1 make[2]: Leaving directory `/var/tmp/portage/gnome-vfs-2.12.1.1/work/gnome-vfs-2.12.1.1/modules' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gnome-vfs-2.12.1.1/work/gnome-vfs-2.12.1.1' make: *** [all] Error 2 i search the google, i find this: http://www.usenetlinux.com/archive/topic.php/t-492900.html Right, you found something to tell you that you need to run fix_libtools_files.sh. Good! (LOL, it was me, too!). That is the the thing to do whenever you see an error containing this output: ..libstdc++.la' is not a valid libtool archive make[2]: *** [libfile.la] Error 1 and i make this: sayusi bundi # fix_libtool_files.sh 3.3.6 * Scanning libtool files for hardcoded gcc library paths... This is where you wen't wrong. If you need to run the script with further parameters, the usage is: Usage: fix_libtool_files.sh old-gcc-version [--oldarch old-CHOST] (taken from reading the script with less) But the thing is, your problem is not with gcc 3.3.6, as you put in the command; if the problem is that you upgraded gcc (did you?), the proper old version of gcc is listed in the error message: 3.3.5-20050130 So if libtool is failing because you upgraded gcc, the command should be fix_libtool_files.sh 3.3.5-20050130 But if libtool is failing because you changed your CHOST (with or without upgrading gcc), the command should be fix_libtool_files.sh --oldarch i386-pc-linux-gnu So you might try running the script with the correct command and see if that helps more :-) . Holly -- gentoo-user@gentoo.org mailing list
