| 1 |
On Tue, 05 Sep 2006, Meino Christian Cramer wrote: |
| 2 |
|
| 3 |
> due to my installation fault half a year ago, I have to change CHOST |
| 4 |
> from i386* to i686* to be able to install gcc-4.1 & Co. since a |
| 5 |
> better CPU as i386* is needed. |
| 6 |
> |
| 7 |
> As discussed previously it was suggested to change CHOST and do |
| 8 |
> a emerge -e system; emerge -e world then following the gcc-upgrade- |
| 9 |
> and gentoo-upgrade-guide. |
| 10 |
> |
| 11 |
> I tried that (after doing a backup of my whole system), but failed as |
| 12 |
> soon gcc was needed, cause the corrected CHOST implies, that there is |
| 13 |
> gcc already there, which supports (at least by its name...) the "new" |
| 14 |
> CPU. But my old ( == current, not upgraded) gcc is named after the |
| 15 |
> wrong CHOST nameing (i386-pc-linux-gnu). |
| 16 |
> |
| 17 |
|
| 18 |
Use fix_libtool_files.sh. Running it without arguments gives you |
| 19 |
usage. |
| 20 |
|
| 21 |
Mikko |
| 22 |
|
| 23 |
-- |
| 24 |
Mikko Ruuska, R & D |
| 25 |
Solid Information Technology -- http://www.solidtech.com |
| 26 |
-- |
| 27 |
gentoo-user@g.o mailing list |
Archives