From: Christoph Hellwig <hch@lst.de>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>, Shuah Khan <shuah@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
bpf@vger.kernel.org
Subject: Re: BPF selftests build failures
Date: Tue, 21 Jul 2020 09:04:37 +0200 [thread overview]
Message-ID: <20200721070437.GA11432@lst.de> (raw)
In-Reply-To: <20200720204152.w7h3zmwtbjsuwgie@ast-mbp.dhcp.thefacebook.com>
On Mon, Jul 20, 2020 at 01:41:52PM -0700, Alexei Starovoitov wrote:
> On Mon, Jul 20, 2020 at 10:09:43AM +0200, Christoph Hellwig wrote:
> > Hi BPF and selftest maintainers. I get a very strange failure
> > when trying to build the bpf selftests on current net-next master:
> >
> > hch@brick:~/work/linux/tools/testing/selftests/bpf$ make
> > GEN vmlinux.h
> > Error: failed to load BTF from /home/hch/work/linux/vmlinux: No such file or directory
>
> That's bpftool complaining that BTF is not present in vmlinux.
> You need CONFIG_DEBUG_INFO_BTF=y and pahole >= v1.16
> You also need llvm 10 to build bpf progs.
Oh well, after the non-obvious enabling of CONFIG_DEBUG_INFO_BTF
I did run into the too old clang (clang 9) as well, which just
creates random errors instead of warning about a too old compiler,
sight.
Then I installed clang-10, but there still seem to be various
failures in the net-next baseline, and the setsockopt code I'm
trying to test doesn't even get exercised from sticking a printk
in there.
That is not a great testcase experience..
prev parent reply other threads:[~2020-07-21 7:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 8:09 BPF selftests build failures Christoph Hellwig
2020-07-20 20:41 ` Alexei Starovoitov
2020-07-21 2:54 ` David Ahern
2020-07-21 5:24 ` Christoph Hellwig
2020-07-21 7:04 ` Christoph Hellwig [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=20200721070437.GA11432@lst.de \
--to=hch@lst.de \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=shuah@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