| 1 |
On 9/12/06, Richard Fish <bigfish@××××××××××.org> wrote: |
| 2 |
> On 9/12/06, darren kirby <bulliver@×××××××××××.org> wrote: |
| 3 |
> > system. The cpu instructions are forward (but not backward) compatible. Thus, |
| 4 |
> > I did not think it necessary for a wholesale rebuild of the entire system on |
| 5 |
> > the spot. Indeed it seems this is not as simple as I thought. I may have been |
| 6 |
> > thinking changing CHOST was as simple as changing -march or -mcpu... |
| 7 |
> |
| 8 |
> Well I've brought up the issue on -dev, and it seems that something |
| 9 |
> official is in the works on this, so we'll see what comes of that. |
| 10 |
> Maybe your answer will turn out to be correct! |
| 11 |
|
| 12 |
And indeed, the emerge -e world may in fact be optional. |
| 13 |
|
| 14 |
A quite from the current draft of the guide [1]: |
| 15 |
|
| 16 |
""" |
| 17 |
- You may want to run |
| 18 |
# emerge -e world |
| 19 |
now. In theory it should not be necessary to do so, but it can not be |
| 20 |
100% guaranteed that this is actually the case. ;-) |
| 21 |
""" |
| 22 |
|
| 23 |
I think I'd still like to see people run an emerge -e system |
| 24 |
regardless...just as an extra safety step to make sure the system |
| 25 |
packages are sane. But my understanding of what can be affected by a |
| 26 |
change in CHOST is definitely changed. |
| 27 |
|
| 28 |
-Richard |
| 29 |
|
| 30 |
[1] http://dev.gentoo.org/~amne/temp/change-chost.txt |
| 31 |
-- |
| 32 |
gentoo-user@g.o mailing list |
Archives