From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
Namhyung Kim <namhyung.kim@lge.com>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Thomas Ilsche <thomas.ilsche@tu-dresden.de>
Subject: Re: [PATCH v2 1/2] perf tools: Fix make PYTHON override
Date: Thu, 31 Jul 2014 11:38:08 -0300 [thread overview]
Message-ID: <20140731143808.GA20547@kernel.org> (raw)
In-Reply-To: <1406617040-26909-1-git-send-email-namhyung@kernel.org>
Em Tue, Jul 29, 2014 at 03:57:19PM +0900, Namhyung Kim escreveu:
> Thomas reported that make PYTHON=python2 is not work on some systems.
> I can reproduce it on my ArchLinux box too.
>
> This is because it's overridden by config/feature-checks/Makefile
> regardless of PYTHON setting. I guess it's a bug slipped into during
> the feature checking change.
>
> Actually, we don't need to check python-config in the feature-checks.
> We can just pass appropriate FEATURE_CHECK_*FLAGS.
>
> Reported-by: Thomas Ilsche <thomas.ilsche@tu-dresden.de>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Thanks, both patches applied.
- Arnaldo
next prev parent reply other threads:[~2014-07-31 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 6:57 [PATCH v2 1/2] perf tools: Fix make PYTHON override Namhyung Kim
2014-07-29 6:57 ` [PATCH v2 2/2] perf tools: Default to python version 2 Namhyung Kim
2014-08-01 20:21 ` Arnaldo Carvalho de Melo
2014-08-02 10:56 ` Thomas Ilsche
2014-08-02 13:20 ` Arnaldo Carvalho de Melo
2014-08-04 13:03 ` [PATCH v3 " Thomas Ilsche
2014-08-04 15:35 ` Arnaldo Carvalho de Melo
2014-08-13 5:19 ` [tip:perf/core] " tip-bot for Thomas Ilsche
2014-07-31 14:38 ` Arnaldo Carvalho de Melo [this message]
2014-08-13 5:17 ` [tip:perf/core] perf tools: Fix make PYTHON override tip-bot for 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=20140731143808.GA20547@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=thomas.ilsche@tu-dresden.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.