[PATCH] Raise the minimum GCC version to 5.2
Miguel Ojeda
miguel.ojeda.sandonis at gmail.com
Tue May 4 09:38:32 BST 2021
On Tue, May 4, 2021 at 9:57 AM Ben Dooks <ben.dooks at codethink.co.uk> wrote:
>
> Some of us are a bit stuck as either customer refuses to upgrade
> their build infrastructure or has paid for some old but safety
> blessed version of gcc. These often lag years behind the recent
> gcc releases :(
In those scenarios, why do you need to build mainline? Aren't your
customers using longterm or frozen kernels? If they are paying for
certified GCC images, aren't they already paying for supported kernel
images from some vendor too?
I understand where you are coming from -- I have also dealt with
projects/machines running ancient, unsupported software/toolchains for
various reasons; but nobody expected upstream (and in particular the
mainline kernel source) to support them. In the cases I experienced,
those use cases require not touching anything at all, and when the
time came of doing so, everything would be updated at once,
re-certified/validated as needed and frozen again.
Cheers,
Miguel
More information about the linux-riscv
mailing list