From: Steven Rostedt <rostedt@goodmis.org>
To: Namhyung Kim <namhyung.kim@lge.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Borislav Petkov <bp@alien8.de>, David Ahern <dsahern@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/7] trace-cmd: Add NO_PYTHON option for Makefile
Date: Tue, 10 Apr 2012 13:36:16 -0400 [thread overview]
Message-ID: <1334079376.23924.220.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1333940074-19052-2-git-send-email-namhyung.kim@lge.com>
On Mon, 2012-04-09 at 11:54 +0900, Namhyung Kim wrote:
> If someone do not want to build python plugins, [s]he can
> define the option to disable python support:
>
> $ make NO_PYTHON=1
Thanks, I should also add a way to check if this will compile, or if it
fails to just print a message to build with this.
-- Steve
>
> Signed-off-by: Namhyung Kim <namhyung.kim@lge.com>
> ---
> Makefile | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index edf3402..54dbba4 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -76,6 +76,7 @@ ifndef VERBOSE
> VERBOSE = 0
> endif
>
> +ifndef NO_PYTHON
> PYTHON := ctracecmd.so
> PYTHON_GUI := ctracecmd.so ctracecmdgui.so
>
> @@ -86,6 +87,7 @@ ifeq ($(shell sh -c "python-config --includes > /dev/null 2>&1 && echo y"), y)
> PYTHON_SO_INSTALL := ctracecmd.install
> PYTHON_PY_INSTALL := event-viewer.install tracecmd.install tracecmdgui.install
> endif
> +endif # NO_PYTHON
>
> # $(call test-build, snippet, ret) -> ret if snippet compiles
> # -> empty otherwise
next prev parent reply other threads:[~2012-04-10 17:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 2:54 [PATCH 0/7] trace-cmd: Small fixes and cleanups on libparsevent Namhyung Kim
2012-04-09 2:54 ` [PATCH 1/7] trace-cmd: Add NO_PYTHON option for Makefile Namhyung Kim
2012-04-10 17:36 ` Steven Rostedt [this message]
2012-04-09 2:54 ` [PATCH 2/7] parse-events: Fix printk_cmp() Namhyung Kim
2012-04-10 17:36 ` Steven Rostedt
2012-07-06 11:12 ` [tip:perf/core] tools lib traceevent: " tip-bot for Namhyung Kim
2012-04-09 2:54 ` [PATCH 3/7] parse-events: Introduce extend_token() Namhyung Kim
2012-07-06 11:13 ` [tip:perf/core] tools lib traceevent: " tip-bot for Namhyung Kim
2012-04-09 2:54 ` [PATCH 4/7] parse-events: Handle strdup failure cases Namhyung Kim
2012-04-23 15:51 ` Steven Rostedt
2012-04-24 0:35 ` Namhyung Kim
2012-04-24 0:41 ` Steven Rostedt
2012-07-06 11:14 ` [tip:perf/core] tools lib traceevent: " tip-bot for Namhyung Kim
2012-04-09 2:54 ` [PATCH 5/7] parse-events: Fix a possible memory leak Namhyung Kim
2012-04-09 2:54 ` [PATCH 6/7] parse-events: Handle realloc() failure path Namhyung Kim
2012-07-06 11:15 ` [tip:perf/core] tools lib traceevent: " tip-bot for Namhyung Kim
2012-04-09 2:54 ` [PATCH 7/7] parse-events: Fix a possibly wrong memory dereference Namhyung Kim
2012-04-09 17:22 ` [PATCH 0/7] trace-cmd: Small fixes and cleanups on libparsevent Frederic Weisbecker
2012-04-10 0:53 ` Namhyung Kim
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=1334079376.23924.220.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=acme@infradead.org \
--cc=bp@alien8.de \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.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
all inboxes | Powered by JetHome®