From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S941327AbdAGKWA (ORCPT ); Sat, 7 Jan 2017 05:22:00 -0500 Received: from mx2.suse.de ([195.135.220.15]:34918 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932441AbdAGKVx (ORCPT ); Sat, 7 Jan 2017 05:21:53 -0500 Date: Sat, 7 Jan 2017 11:21:49 +0100 From: Michal Hocko To: Kees Cook Cc: LKML Subject: Re: next: s390 allyesconfig fails to compile samples/seccomp Message-ID: <20170107102147.GB11940@dhcp22.suse.cz> References: <20170106150417.GQ5556@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 06-01-17 12:18:42, Kees Cook wrote: > On Fri, Jan 6, 2017 at 7:04 AM, Michal Hocko 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 /* 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 /* for __BITS_PER_LONG */ -- Michal Hocko SUSE Labs