Command that I ran: ======================================================= # emerge sys-devel/gcc:4.5 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] dev-libs/mpc-0.9 0 kB [ebuild NS ] sys-devel/gcc-4.5.2 [3.4.6-r2, 4.1.2, 4.4.5] USE="fortran gtk mudflap (multilib) nls nptl openmp (-altivec) -bootstrap -build -doc (-fixed-point) -gcj -graphite (-hardened) (-libffi) -lto -multislot -nocxx -nopie -nossp -objc -objc++ -objc-gc -test -vanilla" 0 kB Total: 2 packages (1 new, 1 in new slot), Size of downloads: 0 kB The following keyword changes are necessary to proceed: #required by sys-devel/gcc:4.5 (argument) >=sys-devel/gcc-4.5.2:4.5 ~amd64 NOTE: This --autounmask behavior can be disabled by setting EMERGE_DEFAULT_OPTS="--autounmask=n" in make.conf. Use --autounmask-write to write changes to config files (honoring CONFIG_PROTECT). ======================================================= System config: ======================================================= # emerge --info | grep KEYWORDS ACCEPT_KEYWORDS="amd64 ~amd64" ======================================================= ======================================================= # emerge --version Portage 2.1.10.10 (default/linux/amd64/10.0/developer, gcc-4.4.5, glibc-2.12.2-r0, 3.0.0 x86_64) ======================================================= Strange enough, passing ACCEPT_KEYWORDS=~amd64 from the environment serves as a workaround. Any ideas?
(In reply to comment #0) > The following keyword changes are necessary to proceed: > #required by sys-devel/gcc:4.5 (argument) > >=sys-devel/gcc-4.5.2:4.5 ~amd64 It's trying to say that there's no sys-devel/gcc:4.5 ebuild having ~amd64 in its KEYWORDS. It looks different these days since --autounmask is enabled by default. Maybe we can clarify it somehow?
# grep KEYWORDS /usr/portage/sys-devel/gcc/gcc-4.5.2.ebuild KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~x86-fbsd"
Maybe there's a conflicting local setting in /etc/portage. Try this: grep -r sys-devel/gcc /etc/portage
(In reply to comment #3) > Maybe there's a conflicting local setting in /etc/portage. Try this: > > grep -r sys-devel/gcc /etc/portage Oh my, I really did that: # grep -r sys-devel/gcc /etc/portage /etc/portage/package.keywords/sys-devel--gcc:sys-devel/gcc -~amd64 Not sure why I didn't use .mask, instead. Closing, sorry for wasting your time.
