On Mon, 8 Mar 2021 16:44:35 -0700, Grant Taylor wrote: > > It means you probably spent a lot of time compile gcc versions only > > to carry on using the old version, but as you said, this wasn't about > > efficiency. > > Wouldn't the next execution of gcc, post Emerge & Installation use the > newly emerged binary? > > If not next package in a given emerge run didn't use the new gcc, I > would fully expect that subsequent emerges would use the new gcc.
Not if you went up a slot, then the old version would still continue to be used until you ran gcc-config. However, if you were depcleaning at each step, that would remove the previous slot and you would stay current. I tend to keep old copies of gcc around until I'm sure things play nicely with the new version: % gcc-config -l [1] x86_64-pc-linux-gnu-9.3.0 [2] x86_64-pc-linux-gnu-10.2.0 * -- Neil Bothwick Psychiatrists say that 1 of 4 people are mentally ill. Check three friends. If they're OK, you're it.
pgp1liLQnwr6t.pgp
Description: OpenPGP digital signature
