On Wed, 17 May 2023, 07:45 Chris Halse Rogers, <email address hidden>
wrote:
> It looks like this is ready to go for Jammy and is already fixed in
> Lunar, but what's the Kinetic status? From what I can tell this applies
> to kinetic but there are no uploads to kinetic-proposed. Are you
> intending to deliberately leave this unfixed in kinetic?
>
`gcc` has always been fixed in kinetic.
The default GCC is what matters here. It is gcc-11 in jammy based off
whatever devel packaging has.
In kinetic this is already fixed in the default GCC, which is gcc-12 as
used to build the kernel.
We do not support building kernels with arbitrary toolchains, thus there is
no support requirement to keep gcc-11 (non default) updated in kinetic,
even as we update gcc-11 (default) in jammy & devel.
On Wed, 17 May 2023, 07:45 Chris Halse Rogers, <email address hidden>
wrote:
> It looks like this is ready to go for Jammy and is already fixed in
> Lunar, but what's the Kinetic status? From what I can tell this applies
> to kinetic but there are no uploads to kinetic-proposed. Are you
> intending to deliberately leave this unfixed in kinetic?
>
`gcc` has always been fixed in kinetic.
The default GCC is what matters here. It is gcc-11 in jammy based off
whatever devel packaging has.
In kinetic this is already fixed in the default GCC, which is gcc-12 as
used to build the kernel.
We do not support building kernels with arbitrary toolchains, thus there is
no support requirement to keep gcc-11 (non default) updated in kinetic,
even as we update gcc-11 (default) in jammy & devel.