| 1 |
On Tue, 2006-09-05 at 05:18 +0200, Meino Christian Cramer wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> due to my installation fault half a year ago, I have to change CHOST |
| 5 |
> from i386* to i686* to be able to install gcc-4.1 & Co. since a |
| 6 |
> better CPU as i386* is needed. I am running an |
| 7 |
> AMD Athlon(tm) 64 X2 Dual Core Processor 3800+. |
| 8 |
> |
| 9 |
> As discussed previously it was suggested to change CHOST and do |
| 10 |
> a emerge -e system; emerge -e world then following the gcc-upgrade- |
| 11 |
> and gentoo-upgrade-guide. |
| 12 |
> |
| 13 |
> I tried that (after doing a backup of my whole system), but failed as |
| 14 |
> soon gcc was needed, cause the corrected CHOST implies, that there is |
| 15 |
> gcc already there, which supports (at least by its name...) the "new" |
| 16 |
> CPU. But my old ( == current, not upgraded) gcc is named after the |
| 17 |
> wrong CHOST nameing (i386-pc-linux-gnu). |
| 18 |
> |
| 19 |
> Naturally none of the tools was able to find the "new" gcc -- or |
| 20 |
> using the old one instead. |
| 21 |
> |
| 22 |
> The situation now is: |
| 23 |
> To upgrade to the new gcc-4.1 I & Co. have to change CHOST in |
| 24 |
> beforehand. After changing CHOST no compiler will be found and I |
| 25 |
> will no longer be able to upgrade to gcc-4.1 & Co. |
| 26 |
> |
| 27 |
> Recursive doom ? |
| 28 |
|
| 29 |
I have no guarantee that this will work, but try the following: |
| 30 |
|
| 31 |
0. Make sure backup is up to date |
| 32 |
1. Change CHOST in /etc/make.conf |
| 33 |
2. cd /usr/portage/scripts |
| 34 |
3. ./bootstrap.sh |
| 35 |
4. emerge -e system |
| 36 |
5. emerge -e world |
| 37 |
|
| 38 |
Regards, |
| 39 |
Paul |
| 40 |
|
| 41 |
-- |
| 42 |
gentoo-user@g.o mailing list |
Archives