On 3/8/21 5:35 PM, Neil Bothwick wrote:
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.
So my overall method, which included depclean, did allow subsequent runs
to use the new updated GCC.
Thank you for clarifying.
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 *
[1] aarch64-unknown-linux-gnu-9.3.0 * (cyan *)
[2] x86_64-pc-linux-gnu-10.2.0 * (green *)
The aarch64* came in as part of @openwrt-prerequisites. I should
probably remove that as I no longer need it.
Thank you for your input Neil.
--
Grant. . . .
unix || die
