Allan Gottlieb <[email protected]> writes:
> Today's emerge update world merged gcc-4.5-1.
> (I do have the build system package feature enabled.)
>
> emerge --ignore-default-opts --depclean --ask; revdep-rebuild -- --ask
>
> asked to unmerge 4.5.1 and keep 4.5.1-r1.
>
> I said yes and am now in trouble since my gcc-profile is invlaid
> ajglap gottlieb # gcc-config -l
> * gcc-config: Active gcc profile is invalid!
>
> [1] x86_64-pc-linux-gnu-4.5.1
> ajglap gottlieb #
>
> What should I do?
>
> thanks,
> allan
>
> PS I do have another machine with this same arch amd64.
> However the main machine (the on in trouble) is amd64~ and the others
> are stable.
I hope all is well. It appears I ran the wrong fix_libtool_files.sh
I first ran fix_libtool_files.sh 4.4.5 (which was an older version)
I now ran fix_libtool_files.sh 4.5.1, which seems to have fixed it.
The upgrade was from 4.5.1-->4.5.1-r1 so I guess 4.5.1 is the old
version.
What confused me is that it is also the "new" version since as far as
gcc-config is concerned the -r1 "doesn't count".
That is now, with the machine working again,
ajglap x86_64-pc-linux-gnu # gcc-config -l
[1] x86_64-pc-linux-gnu-4.5.1 *
which is what led me to believe that I needed an older version for
gcc-config.
I guess it is simply "user error" but it was scary.
So what is the right way to emerge a new gcc. Is it
1. do gcc-config -l to find the current active config
and remember that version
2. do the emerge with buildsyspkg feature
3. run fix_libtool_files.sh with the version number from step 1.
(even if it is the same as the current number from gcc-config).
Thanks.
allan
