mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: next: s390 allyesconfig fails to compile samples/seccomp
Date: Sat, 7 Jan 2017 11:21:49 +0100	[thread overview]
Message-ID: <20170107102147.GB11940@dhcp22.suse.cz> (raw)
In-Reply-To: <CAGXu5jLgE6MHBF0_Cgcto49EtrKgcdCNuEH1+Tr7251Xb=yh4g@mail.gmail.com>

On Fri 06-01-17 12:18:42, Kees Cook wrote:
> On Fri, Jan 6, 2017 at 7:04 AM, Michal Hocko <mhocko@kernel.org> 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

      parent reply	other threads:[~2017-01-07 10:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06 15:04 Michal Hocko
2017-01-06 20:18 ` Kees Cook
2017-01-06 20:53   ` Kees Cook
2017-01-07 10:21   ` Michal Hocko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170107102147.GB11940@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®