That's because gcc-3.3 does not have ~x86 in it's KEYWORDS in the ebuild. Check out where it says KEYWORDS="-*" in there.
That's what's wrong. On Wed, 2003-07-30 at 23:45, Jonathan Kelly wrote: > On Wed, 30 Jul 2003 17:26:49 +0200 > "Christian Aust" <[EMAIL PROTECTED]> wrote: > > > Dhruba Bandopadhyay <[EMAIL PROTECTED]> wrote on Wed, 30 Jul 2003 > > 16:14:29 +0100: > > > > > In /etc/portage/package.unmask I have added: > > > > > > >=sys-devel/gcc-3.3 > > > > > > However, gcc 3.3 is still masked. How to unmask it? > > > > *sigh* masking really seems to be an all-time-classic: Please see bug > > #25041, from where > > I've quoted this: > > > > package.unmask only works for packages masked in > > /usr/portage/profiles/package.mask, not for ~arch masking. > > Actually, I think you've got this the wrong way around. I'm pretty sure > from my testing it only unmasks ~x86 masking. I can't get gcc-3.3 to > unmask using /etc/portage/package.mask and it's masked in > /etc/make.profile/packages. I *CAN* unmask gimp-1.3.17 using > /etc/portage/package.mask and it ISN'T masked in > /etc/make.profile/packages. > > Cheers. > Jonathan. > > > > > I'd really like to see the portage guys fix this odd behaviour. Best > > regards, > > > > - Christian > > > > -- > > > > Christian Aust > > mailto:[EMAIL PROTECTED] > > icq: 84500990 - Yahoo!: datenimperator - MSN: datenimperator > > PGP: A073 F9CD 2F23 25D2 EB95 E7A3 B9B4 2AF3 E103 DB5A > > > > -- > > [EMAIL PROTECTED] mailing list > > > > > > -- > [EMAIL PROTECTED] mailing list > -- [EMAIL PROTECTED] mailing list
