From: David Ahern <dsahern@gmail.com>
To: Alexander Alemayhu <alexander@alemayhu.com>
Cc: "Mickaël Salaün" <mic@digikod.net>,
"Alexei Starovoitov" <ast@fb.com>,
"Daniel Borkmann" <daniel@iogearbox.net>,
linux-kernel@vger.kernel.org,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
"Wang Nan" <wangnan0@huawei.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH v1] samples/bpf: Add a .gitignore for binaries
Date: Thu, 18 May 2017 13:03:31 -0700 [thread overview]
Message-ID: <1ce3f092-3552-173f-b26a-48ec81d49f55@gmail.com> (raw)
In-Reply-To: <20170517081844.GA4447@gmail.com>
On 5/17/17 1:18 AM, Alexander Alemayhu wrote:
> I have looked into this but found it to be not easy and all attempts to
> change the Makefile has resulted in obscure errors :/
>
> Getting clang to output in a different directory was easy[0], but I guess
> this is not the right approach either. Have you tried making the change?
spent an hour so a few weeks back. It is not trivial, but someone needs
to find to fix it now.
perf is the example to use: you can build it from both top level kernel
directory (e.g, make -C tools/perf O=/tmp/perf) and the perf directory
(cd tools/perf; make O=/tmp/perf). Both are wanted for samples/bpf and
it would be nice to keep the O= option as well.
I don't have the time for the next few weeks. Perhaps mid-June I can
take a look.
prev parent reply other threads:[~2017-05-18 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 21:23 [PATCH v1] samples/bpf: Add a .gitignore for binaries Mickaël Salaün
2017-02-13 1:43 ` David Ahern
2017-05-13 10:30 ` Mickaël Salaün
2017-05-16 23:27 ` David Ahern
2017-05-17 8:18 ` Alexander Alemayhu
2017-05-18 20:03 ` David Ahern [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=1ce3f092-3552-173f-b26a-48ec81d49f55@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@redhat.com \
--cc=alexander@alemayhu.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mic@digikod.net \
--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).