| 1 |
On Tue, 2005-11-22 at 09:17 +0000, Neil Bothwick wrote: |
| 2 |
> On Tue, 22 Nov 2005 00:28:26 +0100, Matthias Langer wrote: |
| 3 |
> |
| 4 |
> > > As I understand it, the first time you recompile new toolchain with |
| 5 |
> > > your old toolchain, and then the 2nd time you're recompiling the |
| 6 |
> > > toolchain with the new toolchain, with the idea that the new toolchain |
| 7 |
> > > will compile/assemble/link/etc everything in a different way than the |
| 8 |
> > > old toolchain. |
| 9 |
> > > |
| 10 |
> > > Please correct if I'm wrong. |
| 11 |
> > |
| 12 |
> > I would suggest 'emerge -uD gcc && emerge -e world'; This should |
| 13 |
> > recompile the new toolchain with the new toolchain and be considerably |
| 14 |
> > faster. |
| 15 |
> |
| 16 |
> The first command won't do anything, -D doesn't take account of of USE or |
| 17 |
> CFLAG changes. |
| 18 |
|
| 19 |
Well, you are right, in theory; In practice, where the toolchain on the |
| 20 |
live-cd is not up to date, it will get completley recompiled by emerge |
| 21 |
-uD gcc (after syncing) - at least I think so ... |
| 22 |
|
| 23 |
However, thanks for pointing that out ... |
| 24 |
> |
| 25 |
> emerge -e system && emerge -e world might be better, but there are scripts |
| 26 |
> on the forums that recompile just what you need, in the best order, such |
| 27 |
> as; http://forums.gentoo.org/viewtopic-t-282474.html |
| 28 |
> |
| 29 |
Matthias |
| 30 |
|
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
gentoo-user@g.o mailing list |
Archives