| 1 |
On 3/8/21 5:35 PM, Neil Bothwick wrote: |
| 2 |
> Not if you went up a slot, then the old version would still continue to |
| 3 |
> be used until you ran gcc-config. However, if you were depcleaning at each |
| 4 |
> step, that would remove the previous slot and you would stay current. |
| 5 |
|
| 6 |
So my overall method, which included depclean, did allow subsequent runs |
| 7 |
to use the new updated GCC. |
| 8 |
|
| 9 |
Thank you for clarifying. |
| 10 |
|
| 11 |
> I tend to keep old copies of gcc around until I'm sure things play nicely |
| 12 |
> with the new version: |
| 13 |
> |
| 14 |
> % gcc-config -l |
| 15 |
> [1] x86_64-pc-linux-gnu-9.3.0 |
| 16 |
> [2] x86_64-pc-linux-gnu-10.2.0 * |
| 17 |
|
| 18 |
[1] aarch64-unknown-linux-gnu-9.3.0 * (cyan *) |
| 19 |
[2] x86_64-pc-linux-gnu-10.2.0 * (green *) |
| 20 |
|
| 21 |
The aarch64* came in as part of @openwrt-prerequisites. I should |
| 22 |
probably remove that as I no longer need it. |
| 23 |
|
| 24 |
Thank you for your input Neil. |
| 25 |
|
| 26 |
|
| 27 |
|
| 28 |
-- |
| 29 |
Grant. . . . |
| 30 |
unix || die |
Archives