On 07/09/2010 07:45 PM, Valmor de Almeida wrote: > Dale wrote: > [snip] >> >> Is rebuilding the whole system needed for that upgrade tho? >> >> Dale >> >> :-) :-) >> > > Thought it would be a good idea to have a consistent system; not sure > whether it is necessary. > > Thanks for the replies.
The only real need to re-emerge packages is if the new gcc version updates your version of libstdc++, because that lib is supplied by each new version of the gcc package: $ls -l /usr/lib/gcc/i686-pc-linux-gnu/4.4.3/libstdc++* -rw-r--r-- 1 root root 2237388 2010-06-06 13:16 /usr/lib/gcc/i686-pc-linux-gnu/4.4.3/libstdc++.a lrwxrwxrwx 1 root root 19 2010-06-06 13:17 /usr/lib/gcc/i686-pc-linux-gnu/4.4.3/libstdc++.so -> libstdc++.so.6.0.13* lrwxrwxrwx 1 root root 19 2010-06-06 13:17 /usr/lib/gcc/i686-pc-linux-gnu/4.4.3/libstdc++.so.6 -> libstdc++.so.6.0.13* -rwxr-xr-x 1 root root 954472 2010-06-06 13:16 /usr/lib/gcc/i686-pc-linux-gnu/4.4.3/libstdc++.so.6.0.13* -rw-r--r-- 1 root root 2384572 2010-06-06 13:16 /usr/lib/gcc/i686-pc-linux-gnu/4.4.3/libstdc++_pic.a The only packages on your machine that would be affected by the gcc update are those packages that are linked against the OLD version of libstdc++.so. Running revdep-rebuild should rebuild/reinstall all of those packages. Theoretically speaking, of course :)
