1 |
Allan Gottlieb <gottlieb@×××.edu> writes: |
2 |
|
3 |
> Today's emerge update world merged gcc-4.5-1. |
4 |
> (I do have the build system package feature enabled.) |
5 |
> |
6 |
> emerge --ignore-default-opts --depclean --ask; revdep-rebuild -- --ask |
7 |
> |
8 |
> asked to unmerge 4.5.1 and keep 4.5.1-r1. |
9 |
> |
10 |
> I said yes and am now in trouble since my gcc-profile is invlaid |
11 |
> ajglap gottlieb # gcc-config -l |
12 |
> * gcc-config: Active gcc profile is invalid! |
13 |
> |
14 |
> [1] x86_64-pc-linux-gnu-4.5.1 |
15 |
> ajglap gottlieb # |
16 |
> |
17 |
> What should I do? |
18 |
> |
19 |
> thanks, |
20 |
> allan |
21 |
> |
22 |
> PS I do have another machine with this same arch amd64. |
23 |
> However the main machine (the on in trouble) is amd64~ and the others |
24 |
> are stable. |
25 |
|
26 |
I hope all is well. It appears I ran the wrong fix_libtool_files.sh |
27 |
|
28 |
I first ran fix_libtool_files.sh 4.4.5 (which was an older version) |
29 |
|
30 |
I now ran fix_libtool_files.sh 4.5.1, which seems to have fixed it. |
31 |
|
32 |
The upgrade was from 4.5.1-->4.5.1-r1 so I guess 4.5.1 is the old |
33 |
version. |
34 |
|
35 |
What confused me is that it is also the "new" version since as far as |
36 |
gcc-config is concerned the -r1 "doesn't count". |
37 |
That is now, with the machine working again, |
38 |
|
39 |
ajglap x86_64-pc-linux-gnu # gcc-config -l |
40 |
[1] x86_64-pc-linux-gnu-4.5.1 * |
41 |
|
42 |
which is what led me to believe that I needed an older version for |
43 |
gcc-config. |
44 |
|
45 |
I guess it is simply "user error" but it was scary. |
46 |
So what is the right way to emerge a new gcc. Is it |
47 |
|
48 |
1. do gcc-config -l to find the current active config |
49 |
and remember that version |
50 |
|
51 |
2. do the emerge with buildsyspkg feature |
52 |
|
53 |
3. run fix_libtool_files.sh with the version number from step 1. |
54 |
(even if it is the same as the current number from gcc-config). |
55 |
|
56 |
Thanks. |
57 |
|
58 |
allan |