From: Joel Fernandes <email@example.com>
To: LKML <firstname.lastname@example.org>,
"open list:BPF (Safe dynamic programs and tools)"
<email@example.com>, Alexei Starovoitov <firstname.lastname@example.org>,
email@example.com, Chenbo Feng <firstname.lastname@example.org>,
Jakub Kicinski <email@example.com>
Subject: Re: samples don't build on v4.18
Date: Tue, 14 Aug 2018 20:01:32 -0700 [thread overview]
Message-ID: <20180815030132.GA204101@joelaf.mtv.corp.google.com> (raw)
On Tue, Aug 14, 2018 at 06:22:21PM -0700, Joel Fernandes wrote:
> Forgot to add the patch author, doing so now. thanks
> On Tue, Aug 14, 2018 at 6:20 PM, Joel Fernandes <firstname.lastname@example.org> 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 <email@example.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?
There is some weirdness going on with my kernel tree. If I do a fresh clone
of v4.18 and build samples, everything works.
However if I take my existing checkout, do a:
git clean -f -d
Then I try to build the samples, I get the "No libelf found".
Obviously the existing checked out kernel tree is in some weird state that I
am not yet able to fix. But atleast if I blow the whole tree and clone again,
I'm able to build...
Is this related to the intermittent "No libelf found" issues that were
next prev parent reply other threads:[~2018-08-15 3:01 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
2018-08-15 3:01 ` Joel Fernandes [this message]
2018-08-15 19:34 ` Jakub Kicinski
2018-08-16 20:55 ` Joel Fernandes
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).