diff options
author | Sam James <sam@gentoo.org> | 2023-02-02 02:00:09 +0300 |
---|---|---|
committer | Kees Cook <keescook@chromium.org> | 2023-02-02 19:31:23 +0300 |
commit | 5a6b64adc18d9adfb497a529ff004d59b6df151f (patch) | |
tree | 2f16b2f4013a851d49c58ec50e6b358a8c563518 /fs/fscache/volume.c | |
parent | a8c55407a7230798eb157ed2cf5398a6a2b123b6 (diff) | |
download | linux-5a6b64adc18d9adfb497a529ff004d59b6df151f.tar.xz |
gcc-plugins: drop -std=gnu++11 to fix GCC 13 build
The latest GCC 13 snapshot (13.0.1 20230129) gives the following:
```
cc1: error: cannot load plugin ./scripts/gcc-plugins/randomize_layout_plugin.so
:./scripts/gcc-plugins/randomize_layout_plugin.so: undefined symbol: tree_code_type
```
This ends up being because of https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=b0241ce6e37031
upstream in GCC which changes the visibility of some types used by the kernel's
plugin infrastructure like tree_code_type.
After discussion with the GCC folks, we found that the kernel needs to be building
plugins with the same flags used to build GCC - and GCC defaults to gnu++17
right now. The minimum GCC version needed to build the kernel is GCC 5.1
and GCC 5.1 already defaults to gnu++14 anyway, so just drop the flag, as
all GCCs that could be used to build GCC already default to an acceptable
version which was >= the version we forced via flags until now.
Bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108634
Signed-off-by: Sam James <sam@gentoo.org>
Signed-off-by: Kees Cook <keescook@chromium.org>
Link: https://lore.kernel.org/r/20230201230009.2252783-1-sam@gentoo.org
Diffstat (limited to 'fs/fscache/volume.c')
0 files changed, 0 insertions, 0 deletions