On Tue, Apr 13, 2010 at 7:40 AM, Mark Knecht <[email protected]> wrote: > Notes about what I think happened here: > 1) I missed the message about running perl-cleaner so I had to do that. > 2) I had a gcc build that didn't allow the profile to get set so > emerge -1 gcc fixed that. > 3) After that I tried emerge -e @system, emerge -e @world which failed > with more perl issues, but the same package seemed to be part of > @system and emerge -e @system was clean. A second pass at emerge -e > @world failed the same way. Thinking back to the old days, and I know > folks have negative opinions about this, I did emerge -e @system TWICE > in a row, and then emerge -e @world worked. Go figure. > > I'm going to finish KDE and see if it works. If it does then cool, > I'll stick with ~amd64. If not I'm deleting the partitions and > starting over with stable. I've invested a day and a half in this > experiment and my results are not leaving me comfortable. I need to > the machine to work so I can use it starting this afternoon.
I think you've gotten through the hard part and it should hopefully work well from here. The gcc-config thing I have run into before after a new gcc version (unrelated to migrating from amd64 to ~amd64), but I don't think the ebuild tells you to do that...
