On Tue, Aug 08 2017, Nikos Chantziaras wrote: > On 08/08/17 18:13, allan gottlieb wrote: >> gcc-config -l reports >> [1] x86_64-pc-linux-gnu-4.9.3 >> [2] x86_64-pc-linux-gnu-4.9.4 * >> [3] x86_64-pc-linux-gnu-5.4.0 >> >> The news item from 2015-10-22 suggests (I have gentoolkit-0.3.3) >> # revdep-rebuild --library 'libstdc++.so.6' -- --exclude gcc >> >> Is that the entire procedure needed? In particular, ignoring >> performance, can I avoid emerge --emptytree and just execute? >> >> # gcc-config x86_64-pc-linux-gnu-5.4.0 >> # revdep-rebuild --library 'libstdc++.so.6' -- --exclude gcc > > That usually works. If you want to be 100% sure, you still need a full > @system followed by a @world rebuild. But usually just rebuilding > C++-linked packages will give you a stable system. > > I still recommend a @system rebuild at least though, since it's fast.
So you propose # gcc-config x86_64-pc-linux-gnu-5.4.0 # revdep-rebuild --library 'libstdc++.so.6' -- --exclude gcc # emerge @system I am at 98 of 122 for the revdep-rebuild. I just looked and emerge @system would generate approx 50 merges. The only one that looks long is gcc. That seems unfortunate since I just activated that version of gcc and I believe the gcc ebuild is a bootstrap so gcc-5 was compiled with gcc-5. But I guess it might well link to other items that were compiled with gcc-4. I believe that, even though @world includes @system, emerge @system; emerge @world differs from emerge @world So there are many possibilities 1. Stop after the revdep-rebuild 2. emerge @system 3. emerge --emptytree @system 4. emerge @world 5. emerge --emptytree @world 6. emerge @system; emerge @world 7. emerge --emptytree @system; emerge --emptytree @world Which ones do you recommend? thanks, allan