From: David Miller <davem@davemloft.net>
To: alexei.starovoitov@gmail.com
Cc: daniel@iogearbox.net, sparclinux@vger.kernel.org,
netdev@vger.kernel.org, ast@kernel.org
Subject: Re: [PATCH RFC] sparc64: eBPF JIT
Date: Fri, 21 Apr 2017 15:41:52 -0400 (EDT) [thread overview]
Message-ID: <20170421.154152.510081812790700678.davem@davemloft.net> (raw)
In-Reply-To: <20170421192619.GA91454@ast-mbp.thefacebook.com>
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Date: Fri, 21 Apr 2017 12:26:21 -0700
> It should pick up local headers without touching /usr/include.
> In the past I used to do 'make headers_install' before doing a build
> in samples/bpf or selftests, but then suddenly it started working
> without that step, so I figured something got fixed in the build system.
> May be it's arch specific somehow.
Yes, that's what the issue seemed to be.
I ran something unrelated and that triggered a headers_install, and
after that everything built fine.
I have some minor patches coming, to define arch specific accessors
for bpf_helpers.h and such.
next prev parent reply other threads:[~2017-04-21 19:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 3:38 [PATCH RFC] sparc64: eBPF JIT David Miller
2017-04-17 18:44 ` Daniel Borkmann
2017-04-17 19:03 ` David Miller
2017-04-17 20:55 ` Daniel Borkmann
2017-04-17 20:12 ` David Miller
2017-04-21 16:46 ` David Miller
2017-04-21 16:50 ` Daniel Borkmann
2017-04-21 18:49 ` Alexei Starovoitov
2017-04-21 19:02 ` David Miller
2017-04-21 19:26 ` Alexei Starovoitov
2017-04-21 19:41 ` David Miller [this message]
2017-04-17 23:27 ` Alexei Starovoitov
2017-04-18 1:12 ` David Miller
2017-04-18 5:44 ` Alexei Starovoitov
2017-04-18 18:37 ` David Miller
2017-04-18 22:57 ` Alexei Starovoitov
2017-04-19 2:27 ` David Miller
2017-04-22 1:19 ` David Miller
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=20170421.154152.510081812790700678.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=sparclinux@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).