On Thu, 18 Mar 2021 11:41:29 -0000, David Laight said: > That gcc bug just implies you need a space after "xxx". > That is easily fixable in the sources.
It's not quite that simple.
In file included from /usr/lib/gcc/x86_64-linux-gnu/5/plugin/include/tm.h:27,
from
/usr/lib/gcc/x86_64-linux-gnu/5/plugin/include/gcc-plugin.h:31,
from
/usr/lib/gcc/x86_64-linux-gnu/5/plugin/include/plugin.h:23,
from scripts/gcc-plugins/gcc-common.h:9,
from scripts/gcc-plugins/latent_entropy_plugin.c:78:
>> /usr/lib/gcc/x86_64-linux-gnu/5/plugin/include/config/elfos.h:102:21:
>> warning: invalid suffix on literal; C++11 requires a space between literal
>> and string macro [-Wliteral-suffix]
fprintf ((FILE), "%s"HOST_WIDE_INT_PRINT_UNSIGNED"\n",\
The problem isn't in a kernel source file... To quote an earlier message of
mine:
> It looks like it's not a kernel source tree issue, it's a g++ issue fixed in
> g++ 6 and later.
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69959
> And it looks like there was an intent to backport it to 4.9 and 5.4:
> https://gcc.gnu.org/legacy-ml/gcc-patches/2016-02/msg01409.html
> The bugtracker doesn't show an equivalent for 69959 being closed against
> 4.9.x or 5.[56],
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63254 has a patch for one of the
> gcc-supplied files that tosses the warning, but that way lies madness...
pgpKAMpPEyXho.pgp
Description: PGP signature
