Re: next: s390 allyesconfig fails to compile samples/seccomp

[Michal Hocko]

On Fri 06-01-17 12:18:42, Kees Cook wrote:
> On Fri, Jan 6, 2017 at 7:04 AM, Michal Hocko <mhocko@xxxxxxxxxx> wrote:
> > Hi,
> > I am not relly sure what went wrong, but I've noticed that allyesconfig
> > doesn't compile with my s390 crosscompiler with a strange error
> > messages for linux-next (next-20170106). Linus' tree compiles just fine.
> > It smells like some headers include problems because
> > $ git diff origin/master..next/master -- samples/seccomp/
> > doesn't show anything...
> 
> Oh, how strange. Did __BITS_PER_LONG move around? That's part of uapi...

Yes, and it seems something is broken wrt build system for
samples/seccomp
In file included from samples/seccomp/bpf-fancy.c:20:0:
samples/seccomp/bpf-helper.h:17:60: fatal error: uapi/asm/bitsperlong.h: No such file or directory
 #include <uapi/asm/bitsperlong.h> /* for __BITS_PER_LONG */
                                                            ^
compilation terminated.
make[2]: *** [samples/seccomp/bpf-fancy.o] Error 1
make[2]: *** Waiting for unfinished jobs....
In file included from samples/seccomp/bpf-helper.c:16:0:
samples/seccomp/bpf-helper.h:17:60: fatal error: uapi/asm/bitsperlong.h: No such file or directory
 #include <uapi/asm/bitsperlong.h> /* for __BITS_PER_LONG */

-- 
Michal Hocko
SUSE Labs