Re: [gentoo-user] CHOST recursive problem
On Tue, 05 Sep 2006, Meino Christian Cramer wrote: due to my installation fault half a year ago, I have to change CHOST from i386* to i686* to be able to install gcc-4.1 Co. since a better CPU as i386* is needed. As discussed previously it was suggested to change CHOST and do a emerge -e system; emerge -e world then following the gcc-upgrade- and gentoo-upgrade-guide. I tried that (after doing a backup of my whole system), but failed as soon gcc was needed, cause the corrected CHOST implies, that there is gcc already there, which supports (at least by its name...) the new CPU. But my old ( == current, not upgraded) gcc is named after the wrong CHOST nameing (i386-pc-linux-gnu). Use fix_libtool_files.sh. Running it without arguments gives you usage. Mikko -- Mikko Ruuska, R D Solid Information Technology -- http://www.solidtech.com -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] CHOST recursive problem
Am Dienstag, 5. September 2006 05:18 schrieb ext Meino Christian Cramer: I tried that (after doing a backup of my whole system), but failed as soon gcc was needed, cause the corrected CHOST implies, that there is gcc already there, which supports (at least by its name...) the new CPU. But my old ( == current, not upgraded) gcc is named after the wrong CHOST nameing (i386-pc-linux-gnu). Try providing the correct names via symlinks. HTH... Dirk -- Dirk Heinrichs | Tel: +49 (0)162 234 3408 Configuration Manager | Fax: +49 (0)211 47068 111 Capgemini Deutschland | Mail: [EMAIL PROTECTED] Hambornerstraße 55 | Web: http://www.capgemini.com D-40472 Düsseldorf | ICQ#: 110037733 GPG Public Key C2E467BB | Keyserver: www.keyserver.net pgp2sjU2Af5kl.pgp Description: PGP signature
Re: [gentoo-user] CHOST recursive problem
On Tuesday 05 September 2006 00:33, Jean-Marc Beaune wrote: Hi, Just a stupid question : What is bootstrap.sh used for ? This is the script used to bootstrap your system. Usually this is only used if installing from stage1. -- Zac Slade [EMAIL PROTECTED] ICQ:1415282 YM:krakrjak AIM:ttyp99 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] CHOST recursive problem
On Tue, 2006-09-05 at 05:18 +0200, Meino Christian Cramer wrote: Hi, due to my installation fault half a year ago, I have to change CHOST from i386* to i686* to be able to install gcc-4.1 Co. since a better CPU as i386* is needed. I am running an AMD Athlon(tm) 64 X2 Dual Core Processor 3800+. As discussed previously it was suggested to change CHOST and do a emerge -e system; emerge -e world then following the gcc-upgrade- and gentoo-upgrade-guide. I tried that (after doing a backup of my whole system), but failed as soon gcc was needed, cause the corrected CHOST implies, that there is gcc already there, which supports (at least by its name...) the new CPU. But my old ( == current, not upgraded) gcc is named after the wrong CHOST nameing (i386-pc-linux-gnu). Naturally none of the tools was able to find the new gcc -- or using the old one instead. The situation now is: To upgrade to the new gcc-4.1 I Co. have to change CHOST in beforehand. After changing CHOST no compiler will be found and I will no longer be able to upgrade to gcc-4.1 Co. Recursive doom ? I have no guarantee that this will work, but try the following: 0. Make sure backup is up to date 1. Change CHOST in /etc/make.conf 2. cd /usr/portage/scripts 3. ./bootstrap.sh 4. emerge -e system 5. emerge -e world Regards, Paul -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] CHOST recursive problem
Hi, Just a stupid question : What is bootstrap.sh used for ? Thanks /JM On 9/5/06, Paul Varner [EMAIL PROTECTED] wrote: On Tue, 2006-09-05 at 05:18 +0200, Meino Christian Cramer wrote: Hi,due to my installation fault half a year ago, I have to change CHOST from i386* to i686* to be able to install gcc-4.1 Co. since abetter CPU as i386* is needed. I am running anAMD Athlon(tm) 64 X2 Dual Core Processor 3800+.As discussed previously it was suggested to change CHOST and do a emerge -e system; emerge -e world then following the gcc-upgrade-and gentoo-upgrade-guide.I tried that (after doing a backup of my whole system), but failed assoon gcc was needed, cause the corrected CHOST implies, that there is gcc already there, which supports (at least by its name...) the newCPU. But my old ( == current, not upgraded) gcc is named after thewrong CHOST nameing (i386-pc-linux-gnu). Naturally none of the tools was able to find the new gcc -- orusing the old one instead.The situation now is:To upgrade to the new gcc-4.1 I Co. have to change CHOST in beforehand.After changing CHOST no compiler will be found and Iwill no longer be able to upgrade to gcc-4.1 Co.Recursive doom ?I have no guarantee that this will work, but try the following: 0. Make sure backup is up to date1. Change CHOST in /etc/make.conf2. cd /usr/portage/scripts3. ./bootstrap.sh4. emerge -e system5. emerge -e worldRegards,Paul-- gentoo-user@gentoo.org mailing list
