From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: David Ahern <dsahern@gmail.com>
Cc: Borislav Petkov <bp@amd64.org>, Ingo Molnar <mingo@kernel.org>,
Michal Marek <mmarek@suse.cz>, Sam Ravnborg <sam@ravnborg.org>,
LKML <linux-kernel@vger.kernel.org>,
Borislav Petkov <borislav.petkov@amd.com>
Subject: Re: [PATCH v5 5/5] tools: Connect to the kernel build system
Date: Wed, 11 Apr 2012 16:52:44 -0300 [thread overview]
Message-ID: <20120411195244.GL16257@infradead.org> (raw)
In-Reply-To: <4F85CB23.8030305@gmail.com>
Em Wed, Apr 11, 2012 at 12:19:15PM -0600, David Ahern escreveu:
> On 4/11/12 12:08 PM, Arnaldo Carvalho de Melo wrote:
>
> >>[acme@sandy linux]$ make -j8 O=/home/git/build/perf tools/perf_install
> >>[acme@sandy linux]$ ls -la tools/perf/*.o | wc -l
> >>22
> >>
> >>It should have honoured O=
> >>
> >>Can you fix this one please? :)
> >
> >But that can be on top of this series as the way I use it:
> >
> > make -j8 -C tools/perf/ O=/home/git/build/perf install
> >
> >still works as expected.
>
> Does this sequence still work?
>
> cd tools/perf
> make O=/tmp/pbuild
>
> and the O= is honored?
Yes:
[acme@sandy linux]$ mkdir /tmp/perf
[acme@sandy linux]$ cd tools/perf
[acme@sandy perf]$ make O=/tmp/perf
MKDIR /tmp/perf/arch/x86/util
<SNIP>
MKDIR /tmp/perf/util/ui/browsers
PERF_VERSION = perf.core.for.mingo.6.gea01fa
GEN /tmp/perf/common-cmds.h
* new build flags or prefix
CC /tmp/perf/perf.o
CC /tmp/perf/builtin-annotate.o
<SNIP>
CC /tmp/perf/util/parse-options.o
BISON event-parser
FLEX event-parser
BISON pmu-parser
FLEX pmu-parser
CC /tmp/perf/util/parse-events.o
<SNIP>
AR /tmp/perf/libperf.a
LINK /tmp/perf/perf
GEN perf-archive
GEN /tmp/perf/python/perf.so
[acme@sandy perf]$
[acme@sandy perf]$ /tmp/perf/perf --version
perf version perf.core.for.mingo.6.gea01fa
[acme@sandy perf]$
- Arnaldo
next prev parent reply other threads:[~2012-04-11 19:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 16:36 [PATCH v5 0/5] tools: Add a toplevel Makefile Borislav Petkov
2012-04-11 16:36 ` [PATCH v5 1/5] tools: Add Makefile.include Borislav Petkov
2012-04-13 18:14 ` [tip:perf/core] " tip-bot for Borislav Petkov
2012-04-11 16:36 ` [PATCH v5 2/5] tools: Cleanup EXTRA_WARNINGS Borislav Petkov
2012-04-13 18:15 ` [tip:perf/core] " tip-bot for Borislav Petkov
2012-04-11 16:36 ` [PATCH v5 3/5] tools: Add a toplevel Makefile Borislav Petkov
2012-04-13 18:16 ` [tip:perf/core] " tip-bot for Borislav Petkov
2012-04-11 16:36 ` [PATCH v5 4/5] tools: Add a help target Borislav Petkov
2012-04-13 18:17 ` [tip:perf/core] " tip-bot for Borislav Petkov
2012-04-11 16:36 ` [PATCH v5 5/5] tools: Connect to the kernel build system Borislav Petkov
2012-04-11 18:04 ` Arnaldo Carvalho de Melo
2012-04-11 18:08 ` Arnaldo Carvalho de Melo
2012-04-11 18:19 ` David Ahern
2012-04-11 19:45 ` Borislav Petkov
2012-04-11 19:52 ` Arnaldo Carvalho de Melo [this message]
2012-04-12 15:22 ` Borislav Petkov
2012-04-12 15:57 ` Sam Ravnborg
2012-04-12 18:33 ` Arnaldo Carvalho de Melo
2012-04-12 19:16 ` Sam Ravnborg
2012-04-12 19:31 ` Arnaldo Carvalho de Melo
2012-04-12 21:17 ` Alex Riesen
2012-04-13 10:45 ` Borislav Petkov
2012-04-11 19:47 ` Borislav Petkov
2012-04-13 18:18 ` [tip:perf/core] " tip-bot for Borislav Petkov
2012-04-14 6:35 ` Alex Riesen
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=20120411195244.GL16257@infradead.org \
--to=acme@infradead.org \
--cc=borislav.petkov@amd.com \
--cc=bp@amd64.org \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.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).