On Friday 19 Dec 2014 15:53:53 meino.cra...@gmx.de wrote: > Mick <michaelkintz...@gmail.com> [14-12-19 16:52]: > > On Friday 19 Dec 2014 15:23:58 meino.cra...@gmx.de wrote: > > > Peter Humphrey <pe...@prh.myzen.co.uk> [14-12-19 16:12]: > > > > On Friday 19 December 2014 11:18:34 Mick wrote: > > > > > I run fix_libtool_files.sh after a new gcc > > > > > is installed, BEFORE I remove the old version. I made a bit of a > > > > > habit of this, but I don't know if modern ebuilds of gcc actually > > > > > run the same script post install. > > > > > > > > I've found that emerge -c gcc runs fix_libtool_files.sh > > > > automatically. This has been true for quite a while now. > > > > > > Hi Peter, > > > > > > that implies that running fix_libtool_files.sh right after installing > > > gcc is ok before removing the old gcc. This is the opposite from > > > previous mail. > > > > > > By the way: I could'n find optino "-c" for emerge in the manpages... > > > > Meino, to avoid misunderstandings: > > > > 1. Emerge the new gcc package. > > > > 2. Use gcc-config to change to the new gcc version. > > > > 3. Run 'env-update && source /etc/profile'. > > > > 4. Run fix_libtool_files.sh, although I would think that this is > > redundant these days. > > > > 5. Unmerge the old gcc version. > > Hi Mick, > > thanks for makeing things clear! :) > One man - one word - one gcc version! :)) > > THX!
You're welcome. Peter's right the '--depclean --verbose' options will warn you if something you have already installed depends on the old gcc version. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
