Re: x86: unistd_64.h: warning: missing whitespace after the macro name

[Thomas Gleixner]

On Mon, May 24 2021 at 17:16, Naresh Kamboju wrote:

> While building Linux next-20210524 tag with gcc 7.x the following warnings and
> errors were noticed.
>
> build log:
> ------------
>   HOSTLD  scripts/mod/modpost
>   CC      kernel/bounds.s
>   CALL    /srv/oe/build/tmp-lkft-glibc/work-shared/intel-corei7-64/kernel-source/scripts/atomic/check-atomics.sh
>   UPD     include/generated/bounds.h
>   UPD     include/generated/timeconst.h
>   CC      arch/x86/kernel/asm-offsets.s
> In file included from
> /srv/oe/build/tmp-lkft-glibc/work-shared/intel-corei7-64/kernel-source/arch/x86/include/asm/unistd.h:20:0,
>                  from
> /srv/oe/build/tmp-lkft-glibc/work-shared/intel-corei7-64/kernel-source/arch/x86/include/asm/seccomp.h:5,
>                  from
> /srv/oe/build/tmp-lkft-glibc/work-shared/intel-corei7-64/kernel-source/include/linux/seccomp.h:21,
>                  from
> /srv/oe/build/tmp-lkft-glibc/work-shared/intel-corei7-64/kernel-source/include/linux/sched.h:21,
>                  from
> /srv/oe/build/tmp-lkft-glibc/work-shared/intel-corei7-64/kernel-source/arch/x86/kernel/asm-offsets.c:10:
> ./arch/x86/include/generated/uapi/asm/unistd_64.h:4:14: warning:
> missing whitespace after the macro name
>  #define __NR_/usrread 0
>               ^

Where is that "/usr" coming from? 

Looking at the generator script this looks like a stale $prefix
parameter...