On Wednesday 07 June 2006 21:50, Bob Young wrote: > > On 6/7/06, Roy Wright <[EMAIL PROTECTED]> wrote: > > > You might want to read: > > > > > > http://forums.gentoo.org/viewtopic.php?t=282474&highlight= > > > > > > which basically recommends: > > > > > > emerge -s > > > emerge -s > > > emerge -e > > > emerge -e > > > > Ugh, this is completely pointless. A single "emerge -e world" is > > sufficient. > > Depends on what you consider sufficient. Although what the page recommends > was misquoted, it actually suggests: > > emerge -e system > emerge -e system > emerge -e world > emerge -e world > > That's probably is a little bit excessive, but the reason for doing the two > emerge -e systems is so that the new tool chain is built with the new tool > chain. At the end of the first emerge -e system you may have a new > compiler, but that new compiler was built with the old compiler. What you > actually want is a gcc-4.1.1 that was built with gcc-4.1.1. You could > emerge the compiler twice before doing the emerge -e system, but the the > emerges that happen before glibc is rebuilt are linked against a glibc that > was built with the old compiler. Same with the rest of the tool chain and > libraries. > > That being said "emerge -e system" is probably overkill just for a new > toolchain. Updating a subset of all possible toolchain related things and > then following that by a single emerge -e world would probably be > sufficient for most people. This page: > http://forums.gentoo.org/viewtopic-t-345229.html is about doing an install, > but it shows how to update a subset of the entire tool chain. Note that the > article does in the end, do a double emerge -e system, so the the value of > updating a toolchain subset is questionable for the article's purposes. > > In short: > > emerge gcc-config glibc binutils libstdc++-v3 gcc > emerge gcc-config glibc binutils libstdc++-v3 gcc > emerge -e world > > To be clear, in order to make sure absolutely everything is updated and the > libraries that are linked against are also updated prior to use, the two > emerge -e system commands, are the definitive solution. For those who don't > want to spend many extra hours of compile time, in order to gain a 0.5% > increase in performance, the above is offered for consideration. > > Regards, > Bob Young
Wow! I said the same thing a week or so ago and got the same rebuttal. However, it's what I do none the less. And it works. -- gentoo-user@gentoo.org mailing list
