Bo Ørsted Andresen wrote: > > Oh, and just for the the record. Whatever you do with this don't downgrade > glibc! :p That will make you even more screwed that you are already. I guess > you've learned by now that you should never run --depclean blindly. Always > run it with --pretend first and ensure that it doesn't do something stupid. > Unfortunately this is a little late for that though... :( >
At the time that emerge --depclean was unsafe I used to do: emerge --pretend --depclean | grep / > dc2 remove the first line from dc2 for p in `cat dc2` do echo --------- $p ---------- equery depends $p done > dc3 And I could see what realy could be unmerged. Then I learned from this mailing list that dep -d would take my USE flags into account so I did "dep -d". It showed me the list of things it was going to unmerge and I saw the gcc.3.4 but thought: well, I know I have gcc.4.something and what's the use of having an old C compiler hanging around? So I let it go.... :-( Now to solve the situation I did gcc-config i386-pc-linux-gnu-4.1.1 and emerge is working more or less. Now I'm going to emerge binutils, gcc and glibc in the hope that everything will be allright. Currently, I get lots of "rc-scripts: gcc-config: Active gcc profile is invalid!" in /var/log/messages. -- gentoo-user@gentoo.org mailing list
