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
