From: Greg Kroah-Hartman <gregkh@...>
Sent: 15 December 2021 18:40
On Wed, Dec 15, 2021 at 07:32:23PM +0100, Pavel Machek wrote:
This is the start of the stable review cycle for the 5.10.86 release.I'm getting the gmp.h failures :-(.
There are 33 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
I believe we should not change build requirements in the middle of
To our testing team: 5.10.85 introduced new requirements for the
build. gmp.h is now required in our configs, and maybe something else.
Hi Pavel, sorry for missing this email before now.
I can look into supporting this, depending on the answers to the comments below...
But that commit is needed to get gcc11 plugins to work with the 5.10.y
Easiest fix might be to add
# CONFIG_GCC_PLUGINS is not set
to our configs. Alternatively I know which patch to revert.
But I believe -stable should be the one doing the revert, as the patch
does not fix serious bug and introduces problem. Faster compile is
nice but let mainline have those kind of changes.
kernel tree. So either we "break" it for old and obsolete gcc versions
(i.e. gcc7), or newer supported versions break.
Well this leads us to an interesting point.
At the moment we use GCC v8.1.0 for building all of our kernel trees (cip & stable).
What does CIP want to do mid/long term? Keep upgrading the version we use? Or try and support a specific version of GCC for 10 years?
If the former, when do we want to upgrade?
If the latter, which version?
Kind regards, Chris
We are not in the business of keeping older versions of gcc always