From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Robert Richter <rric@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
hpa@zytor.com, linux-kernel@vger.kernel.org, jolsa@redhat.com,
tglx@linutronix.de, linux-tip-commits@vger.kernel.org,
Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH] perf tools: Fix 'make tools/perf'
Date: Wed, 17 Jul 2013 12:31:18 -0300 [thread overview]
Message-ID: <20130717153118.GC2071@ghostprotocols.net> (raw)
In-Reply-To: <20130716145036.GH8731@rric.localhost>
Em Tue, Jul 16, 2013 at 04:50:36PM +0200, Robert Richter escreveu:
> There are other variant of building perf too:
>
> $ make -C tools perf
> $ make -C tools/perf
>
> Plus variants with O= and DESTDIR set.
>
> This patch fixes the above and was tested with the following:
>
> $ make O=... DESTDIR=... tools/perf
> $ make O=... DESTDIR=... -C tools/ perf
> $ make O=... DESTDIR=... -C tools/perf
> $ make tools/perf
> $ make -C tools/ perf
> $ make -C tools/perf
Thanks, those work now, applied, but can you check all those with actual
targets at the end, i.e. like:
make tools/perf install
Humm, probably it will look at the top level 'install' target? There was
some discussion about this, right? Can you refresh my mind?
- Arnaldo
next prev parent reply other threads:[~2013-07-17 15:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 15:22 [PATCH] perf tools: Fix build errors with O and DESTDIR make vars set Robert Richter
2013-07-12 8:49 ` [tip:perf/urgent] " tip-bot for Robert Richter
2013-07-12 9:39 ` Robert Richter
2013-07-16 14:50 ` [PATCH] perf tools: Fix 'make tools/perf' Robert Richter
2013-07-17 15:31 ` Arnaldo Carvalho de Melo [this message]
2013-07-17 15:40 ` Borislav Petkov
2013-07-17 16:10 ` Robert Richter
2013-07-18 12:19 ` Robert Richter
2013-07-18 16:19 ` Arnaldo Carvalho de Melo
2013-07-18 16:47 ` Robert Richter
2013-07-18 16:41 ` [PATCH] perf tools: Build docs with 'make all' Robert Richter
2013-07-19 7:53 ` [tip:perf/core] perf tools: Fix 'make tools/perf' tip-bot for Robert Richter
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=20130717153118.GC2071@ghostprotocols.net \
--to=acme@infradead.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rric@kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.