netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Martin KaFai Lau <kafai@fb.com>, netdev@vger.kernel.org
Subject: Re: [BUG] bpf is broken in net-next
Date: Mon, 2 Oct 2017 07:52:30 -0700	[thread overview]
Message-ID: <20171002075230.60d36532@xeon-e3> (raw)
In-Reply-To: <20171002013424.tlaictbu7btc4z56@ast-mbp>

On Sun, 1 Oct 2017 18:34:25 -0700
Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:

> On Sun, Oct 01, 2017 at 02:02:30PM -0700, Stephen Hemminger wrote:
> > Recent regression in net-next building bpf.c in samples/bpf now broken.
> > 
> > $ make samples/bpf/
> > 
> > 
> >   HOSTCC  samples/bpf/../../tools/lib/bpf/bpf.o
> > samples/bpf/../../tools/lib/bpf/bpf.c: In function ‘bpf_create_map_node’:
> > samples/bpf/../../tools/lib/bpf/bpf.c:76:13: error: ‘union bpf_attr’ has no member named ‘map_name’; did you mean ‘map_type’?
> >   memcpy(attr.map_name, name, min(name_len, BPF_OBJ_NAME_LEN - 1));
> >              ^
> > samples/bpf/../../tools/lib/bpf/bpf.c:76:44: error: ‘BPF_OBJ_NAME_LEN’ undeclared (first use in this function)
> >   memcpy(attr.map_name, name, min(name_len, BPF_OBJ_NAME_LEN - 1));  
> 
> everything works fine for me...
> did you do 'make headers_install' ?
> 

Yes, that was the problem. I had done make mrproper after changing branches.

      reply	other threads:[~2017-10-02 14:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-01 21:02 [BUG] bpf is broken in net-next Stephen Hemminger
2017-10-02  1:34 ` Alexei Starovoitov
2017-10-02 14:52   ` Stephen Hemminger [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=20171002075230.60d36532@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=kafai@fb.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).