1 |
On Tue, 7 Mar 2017 16:14:26 +0000, White, Phil wrote: |
2 |
|
3 |
> Hi Neil, |
4 |
|
5 |
Please don't top post, it is disliked on this list. |
6 |
|
7 |
> |
8 |
> Well, this is a new install. |
9 |
> Used Stage3-i686-20170214.tar.bz2 |
10 |
> There is nothing in package.accept_keywords that is currently installed |
11 |
> (as far as I know - although it is possible that I might have added |
12 |
> ~x86 to gcc, although in this instance I don't believe that i did) |
13 |
> I have installed some packages, but removed them also (been having |
14 |
> problems with perl) |
15 |
> So currently, updating @world is the same as @system |
16 |
> |
17 |
> OK - talking this through is helping. I *have* done something strange |
18 |
> here. The currently installed version is 4.9.4 (from gcc --version), |
19 |
> except that portage believes that 5.4.0 is installed. |
20 |
> My guess is that, since I am trying to rebuild an old system (due to a |
21 |
> hard-drive fail), I have accidentally copied over files that do not |
22 |
> belong. My guess is a completely useless /var/db/pkg/* is confusing the |
23 |
> hell out of portage/emerge. |
24 |
|
25 |
If you copied over /var/db/pkg you have a rather confused and messed up |
26 |
system. The safest way to recreate it is probably to move the pkg |
27 |
directory elsewhere and then run "emerge -e @world". |
28 |
|
29 |
> So - any suggestions how to fix this mess? |
30 |
> Bite the bullet, emerge gcc, and then do a depclean - or can I convince |
31 |
> portage that gcc 4.9.4 is really here? |
32 |
|
33 |
gcc is slotted, so emerging 4.9.4 will not touch your 5.4.0 installation, |
34 |
you use gcc-config to choose which one to use. What does gcc-config -l |
35 |
show? |
36 |
|
37 |
|
38 |
> |
39 |
> Thanks, |
40 |
> Phil |
41 |
> |
42 |
> On 7 March 2017 at 15:38, Neil Bothwick <neil@××××××××××.uk> wrote: |
43 |
> |
44 |
> > On Tue, 7 Mar 2017 15:07:32 +0000, White, Phil wrote: |
45 |
> > |
46 |
> > > I have a new install of Gentoo. |
47 |
> > > emerge -uDpv --newuse @system results in a new slot for gcc, |
48 |
> > > *downgrading* the current version (from 5.4.0 to 4.9.4) |
49 |
> > > No other package is selected for merging. |
50 |
> > |
51 |
> > 4.9.4 is the latest stable. Are you running a stable system with some |
52 |
> > packages in package.accept_keywords? If so, and you gave a specific |
53 |
> > version of gcc, it is possible that version is no longer in the tree - |
54 |
> > 5.4.0-r2 was recently removed. |
55 |
> > |
56 |
> > Use the ~ operator when specifying versions to allow for minor updates |
57 |
> > |
58 |
> > ~sys-devel/gcc-5.4.0 |
59 |
> > |
60 |
> > or, in the case of gcc, you can specify a slot |
61 |
> > |
62 |
> > sys-devel/gcc:5.4.0 |
63 |
> > |
64 |
> > |
65 |
> > -- |
66 |
> > Neil Bothwick |
67 |
> > |
68 |
> > Despite the cost of living it remains popular. |
69 |
> > |
70 |
|
71 |
|
72 |
|
73 |
|
74 |
-- |
75 |
Neil Bothwick |
76 |
|
77 |
This message has been cruelly tested on sweet little furry animals. |