From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Jiri Benc <jbenc@redhat.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: Network Development <netdev@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH bpf-next 0/7] tools: bpf: standardize make
Date: Thu, 8 Mar 2018 21:10:59 -0800 [thread overview]
Message-ID: <CAADnVQ+=FdTSNzkW2Y6ddLUGaxZv1EdU_Rs-rXzGKmdbEoH6SQ@mail.gmail.com> (raw)
In-Reply-To: <cover.1520545951.git.jbenc@redhat.com>
On Thu, Mar 8, 2018 at 2:00 PM, Jiri Benc <jbenc@redhat.com> wrote:
> Currently, 'make bpf' in the tools/ directory does not provide the standard
> quiet output except for bpftool (which is however listed with a wrong
> directory). Worse, it does not respect the build output directory.
>
> The 'make bpf_install' does not work as one would expect, either. It
> installs unconditionally to /usr/bin without respecting DESTDIR and prefix.
>
> This patchset improves that behavior.
Jakub,
please review this set.
Thanks!
next prev parent reply other threads:[~2018-03-09 5:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 22:00 [PATCH bpf-next 0/7] tools: bpf: standardize make Jiri Benc
2018-03-08 22:00 ` [PATCH bpf-next 1/7] tools: bpftool: silence 'missing initializer' warnings Jiri Benc
2018-03-09 7:38 ` Jakub Kicinski
2018-03-09 8:42 ` Jiri Benc
2018-03-08 22:00 ` [PATCH bpf-next 2/7] tools: bpf: respect output directory during build Jiri Benc
2018-03-08 22:00 ` [PATCH bpf-next 3/7] tools: bpf: consistent make bpf_install Jiri Benc
2018-03-08 22:00 ` [PATCH bpf-next 4/7] tools: bpf: make install should build first Jiri Benc
2018-03-08 22:00 ` [PATCH bpf-next 5/7] tools: bpf: call descend in Makefile Jiri Benc
2018-03-08 22:00 ` [PATCH bpf-next 6/7] tools: bpf: respect quiet/verbose build Jiri Benc
2018-03-08 22:00 ` [PATCH bpf-next 7/7] tools: bpf: silence make by not deleting intermediate file Jiri Benc
2018-03-09 5:10 ` Alexei Starovoitov [this message]
2018-03-09 7:36 ` [PATCH bpf-next 0/7] tools: bpf: standardize make Jakub Kicinski
2018-03-09 9:29 ` Daniel Borkmann
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='CAADnVQ+=FdTSNzkW2Y6ddLUGaxZv1EdU_Rs-rXzGKmdbEoH6SQ@mail.gmail.com' \
--to=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=jakub.kicinski@netronome.com \
--cc=jbenc@redhat.com \
--cc=netdev@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).