On Wednesday 08 March 2006 21:20, "Kumar Golap" <[EMAIL PROTECTED]> wrote about 'Re: [gentoo-user] equery, make.conf USE flag mismatch on amd64': > Thanks all for your help...and I know why now mmx flag was getting > masked. Its in the use.mask as suggested by Martins. > > Attached is the use.mask file i have ...that file gets > updated/overwritten every time i do a "emerge --sync", right ?
Yep. > For now i can live with commenting them out. But I did not realize i > had to do that...i never had to do this before on other machines (not > amd64 though...x86 and ppc64). You don't. In the general case, you can add the flags you want unmasked to /etc/portage/profile/use.mask like so: -win32codecs In this /specific/ case, you don't have to because the ebuilds and gcc know that x86_64 CHOST means that mmx etc. ARE supported and they will hard-enable them (you may not turn them off). Normally, you won't want to mask or unmask USE flags yourself. They are turned on or off by the developers because they are either redundant or broken. I don't know why I didn't jump in the conversation earlier; I guess I hoped someone here could read 'man portage'. There's full documentation for use.mask and over-riding your profile in there. *grumble grumble* -- "If there's one thing we've established over the years, it's that the vast majority of our users don't have the slightest clue what's best for them in terms of package stability." -- Gentoo Developer Ciaran McCreesh -- [email protected] mailing list
