Mick <michaelkintz...@gmail.com> [14-12-19 17:12]: > 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
Hi, backup done! now... gcc-4.8.3 is installed, gcc-config points to the new compiler, the environment is updated (I logged out and in again) and I checked /etc/env.d/04gcc-armv7a-hardfloat-linux-gnueabi for using the new compiler. So everything is fine...except... If I would remove the old compiler now, my system would again be broken. I run the following little loop (zsh) "(.)" means: "only files"): for i in /sbin/*(.) /bin/*(.) /usr/sbin/*(.) /usr/bin/*(.) do ldd $i | grep -q -s '/usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.7.3/libgcc_s.so.1' if [[ "$?" == "0" ]] ; then echo $i >> /tmp/gccfiles6.txt ; fi done I did find 1033 executables still linked against /usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.7.3/libgcc_s.so.1 and may be there are more being linked against other libs of the old compiler. Should I rebuild Gentoo? This would take a very very long time on this little system... How to proceed now? Best Meino