From: Joel Fernandes <joelaf@google.com>
To: LKML <linux-kernel@vger.kernel.org>,
wangnan0@huawei.com,
"open list:BPF (Safe dynamic programs and tools)"
<netdev@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
acme@kernel.org, Chenbo Feng <fengc@google.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: Re: samples don't build on v4.18
Date: Tue, 14 Aug 2018 18:22:21 -0700 [thread overview]
Message-ID: <CAJWu+orb35w6O5B9KyHdYtwc2RbaR9d72HW-i5Bsup72QP8Oag@mail.gmail.com> (raw)
In-Reply-To: <20180815012054.GA70201@joelaf.mtv.corp.google.com>
Forgot to add the patch author, doing so now. thanks
On Tue, Aug 14, 2018 at 6:20 PM, Joel Fernandes <joelaf@google.com> wrote:
>
> Hi,
> When building BPF samples on v4.18, I get the following errors:
>
> $ cd samples/bpf/
> $ make
>
> Auto-detecting system features:
> ... libelf: [ OFF ]
> ... bpf: [ OFF ]
>
> No libelf found
> Makefile:213: recipe for target 'elfdep' failed
> -----------
>
> I bissected it down to commit 5f9380572b4bb24f60cd492b1
>
> Author: Jakub Kicinski <jakub.kicinski@netronome.com>
> Date: Thu May 10 10:24:39 2018 -0700
>
> samples: bpf: compile and link against full libbpf
> ---------
>
> Checking out a kernel before this commit makes the samples build. Also I do
> have libelf on my system.
>
> Any thoughts on this issue?
>
> thank you,
>
> - Joel
next prev parent reply other threads:[~2018-08-15 1:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 1:20 samples don't build on v4.18 Joel Fernandes
2018-08-15 1:22 ` Joel Fernandes [this message]
2018-08-15 3:01 ` Joel Fernandes
2018-08-15 19:34 ` Jakub Kicinski
2018-08-16 20:55 ` Joel Fernandes
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=CAJWu+orb35w6O5B9KyHdYtwc2RbaR9d72HW-i5Bsup72QP8Oag@mail.gmail.com \
--to=joelaf@google.com \
--cc=acme@kernel.org \
--cc=ast@kernel.org \
--cc=fengc@google.com \
--cc=jakub.kicinski@netronome.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wangnan0@huawei.com \
/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).