> > > > > > Three of my systems are having package management trouble. One of > > > > > > the systems does this after revdep-rebuild: > > > > > > > > > > > > All ebuilds that could satisfy "=sys-devel/gcc-4.1.1" have been > > > > > > masked. > > > > > > > > # ls -ld /etc/make.profile > > > > lrwxrwxrwx 1 root root 56 Oct 1 2006 /etc/make.profile -> > > > > /usr/portage/profiles/default-linux/amd64/2006.1/desktop > > > > > > Change to latest stable profile 2007.0/Desktop: > > > rm /etc/make.profile > > > #ln -s /usr/portage/profiles/default-linux/amd64/2007.0/desktop > > > /etc/make.profile > > > > My mistake. That system used this profile: > > > > /usr/portage/profiles/hardened/x86/2.6 > > > > although I just changed it to: > > > > /usr/portage/profiles/hardened/x86/2.6/minimal > > > > because that sounds cooler. Does the hardened profile have something > > to do with it wanting the masked gcc? > > Quite the contrary. The hardened is incompatible with gcc 4.x. Thus > =sys-devel/gcc-4* is masked in all profiles under hardened. Since you have > 4.1.1 installed and no versions in that slot are unmasked it's complaining. > > I think there's a hardened handbook that you should probably read if you want > to use a hardened profile. Switching from non-hardened to hardened is a lot > more involved than changing the symlink.
I think this system (firewall/router) has been on the hardened profile from day 1. Maybe that gcc wasn't always masked in the profile. Should I 'emerge -C =gcc-4.1.1'? - Grant -- [EMAIL PROTECTED] mailing list
