From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Daniel Borkmann <borkmann@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
BPF-dev-list <bpf@vger.kernel.org>
Cc: brouer@redhat.com,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Eric Sage" <eric@sage.org>,
"Andrii Nakryiko" <andrii.nakryiko@gmail.com>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
"Björn Töpel" <bjorn.topel@intel.com>,
"Jiri Olsa" <jolsa@redhat.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Ivan Khoronzhuk" <ivan.khoronzhuk@linaro.org>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>
Subject: Compile build issues with samples/bpf/ again
Date: Wed, 30 Oct 2019 11:43:13 +0100 [thread overview]
Message-ID: <20191030114313.75b3a886@carbon> (raw)
Hi Maintainers,
It is annoy to experience that simply building kernel tree samples/bpf/
is broken as often as it is. Right now, build is broken in both DaveM
net.git and bpf.git. ACME have some build fixes queued from Björn
Töpel. But even with those fixes, build (for samples/bpf/task_fd_query_user.c)
are still broken, as reported by Eric Sage (15 Oct), which I have a fix for.
Could maintainers add building samples/bpf/ to their build test scripts?
(make headers_install && make M=samples/bpf)
Also I discovered, the command to build have also recently changed:
- Before : make samples/bpf/ or simply make in subdir samples/bpf/
- new cmd: make M=samples/bpf and in subdir is broken
Anyone knows what commit introduced this change?
(I need it for a fixes tag, when updating README.rst doc)
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next reply other threads:[~2019-10-30 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 10:43 Jesper Dangaard Brouer [this message]
2019-10-30 10:53 ` Compile build issues with samples/bpf/ again Björn Töpel
2019-10-30 11:05 ` Jesper Dangaard Brouer
2019-10-30 15:07 ` Daniel Borkmann
2019-10-30 15:33 ` Arnaldo Carvalho de Melo
2019-10-31 10:55 ` Daniel Borkmann
2019-10-30 19:09 ` 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=20191030114313.75b3a886@carbon \
--to=brouer@redhat.com \
--cc=acme@redhat.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=borkmann@iogearbox.net \
--cc=bpf@vger.kernel.org \
--cc=eric@sage.org \
--cc=ilias.apalodimas@linaro.org \
--cc=ivan.khoronzhuk@linaro.org \
--cc=jolsa@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=toke@redhat.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).