On Wed, Sep 14, 2011 at 3:19 PM, Neil Bothwick <n...@digimed.co.uk> wrote: > On Wed, 14 Sep 2011 17:03:34 -0500, Dale wrote: > >> I agree with the other post about gcc but you should also update >> portage shortly after that. The newer portage is able to handle more >> issues for you and may save you some time. So, I would update gcc, >> portage then give world a try. If it looks bad, try system first. >> That could correct some things. > > Update portage first, that way you are using the newest version when > updating gcc and glibc. > > Personally, I'd trust portage to know better than me and do > > emerge -au @system > emerge -auDN @world > > -- > Neil Bothwick
Not that I know anything about the OP's environment but on my KDE desktop I've recently (last 6 months or so) found that emerge -fDuN @system won't work as it ends up with unresolvable conflicts. May just be the way I've set up my flags. I completely agree with the sentiment: 1) Update the system's view of portage eix-sync 2) emerge portage 3) Do the rest of the work emerge -fDuN @world emerge -pvDuN @world Fix USE flag issues, if any 4) Do the build emerge -DuN -j13 @world Cheers, Mark
