Hi Neil, Well, this is a new install. Used Stage3-i686-20170214.tar.bz2 There is nothing in package.accept_keywords that is currently installed (as far as I know - although it is possible that I might have added ~x86 to gcc, although in this instance I don't believe that i did) I have installed some packages, but removed them also (been having problems with perl) So currently, updating @world is the same as @system
OK - talking this through is helping. I *have* done something strange here. The currently installed version is 4.9.4 (from gcc --version), except that portage believes that 5.4.0 is installed. My guess is that, since I am trying to rebuild an old system (due to a hard-drive fail), I have accidentally copied over files that do not belong. My guess is a completely useless /var/db/pkg/* is confusing the hell out of portage/emerge. So - any suggestions how to fix this mess? Bite the bullet, emerge gcc, and then do a depclean - or can I convince portage that gcc 4.9.4 is really here? Thanks, Phil On 7 March 2017 at 15:38, Neil Bothwick <n...@digimed.co.uk> wrote: > On Tue, 7 Mar 2017 15:07:32 +0000, White, Phil wrote: > > > I have a new install of Gentoo. > > emerge -uDpv --newuse @system results in a new slot for gcc, > > *downgrading* the current version (from 5.4.0 to 4.9.4) > > No other package is selected for merging. > > 4.9.4 is the latest stable. Are you running a stable system with some > packages in package.accept_keywords? If so, and you gave a specific > version of gcc, it is possible that version is no longer in the tree - > 5.4.0-r2 was recently removed. > > Use the ~ operator when specifying versions to allow for minor updates > > ~sys-devel/gcc-5.4.0 > > or, in the case of gcc, you can specify a slot > > sys-devel/gcc:5.4.0 > > > -- > Neil Bothwick > > Despite the cost of living it remains popular. >
