From: Thomas Ilsche <thomas.ilsche@tu-dresden.de>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Thomas Ilsche <thomas.ilsche@tu-dresden.de>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
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>
Subject: Re: [PATCH 2/2] perf tools: Default to python version 2
Date: Mon, 28 Jul 2014 13:11:05 +0200 [thread overview]
Message-ID: <53D62FC9.2010404@tu-dresden.de> (raw)
In-Reply-To: <87silmibxd.fsf@sejong.aot.lge.com>
[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]
Hi Namhyung,
>>> I'm thinking about something like below.. but sadly it doesn't work for
>>> me.. hmm.
>>
>> Actually this appears to work for me (with 2.6.9 & 2.7.6) and I
>> find this solution more
>> elegant.
>
> Thanks for testing. It was my fault on setting symlink to a
> non-existing file for testing. It now works well for me too.
>
> Can I add your Tested-by then?
Yes
Tested-by: Thomas Ilsche <thomas.ilsche@tu-dresden.de>
Plase note that your patch requires the previous patch that just set the default to python2.
I tested in an Arch Linux VM with:
A) no system install of python, source installation 2.6.9 in PATH
B) no system install of python, source installation 2.7.6 in PATH
C) python3 (as python) and python2 system installation
In all cases it reports to build with libpython and perf script with a dummy Python script
works.
If no python whatsoever is in PATH it reports:
config/Makefile:121: The path 'python' is not executable.
sh: line 0: command: -c: invalid option
command: usage: command [-pVv] command [arg ...]
config/Makefile:122: The path '-config' is not executable.
And the created perf executable does not work with the dummy script.
If only pthon3 is in PATH I get the expected version error message (build stops.)
Note that for the manual old installations of python I had an issue with linking order and
a -Werror issue that I resolved manually. But this is fixed with the latest system install
of python.
Best,
Thomas
>
> Thanks,
> Namhyung
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5015 bytes --]
next prev parent reply other threads:[~2014-07-28 11:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 16:36 Perf: cannot overide PYTHON(_CONFIG) Thomas Ilsche
2014-07-25 3:14 ` [PATCH 1/2] perf tools: Fix make PYTHON override Namhyung Kim
2014-07-25 3:14 ` [PATCH 2/2] perf tools: Default to python version 2 Namhyung Kim
2014-07-25 9:28 ` Thomas Ilsche
2014-07-25 10:24 ` Namhyung Kim
2014-07-25 11:43 ` Thomas Ilsche
2014-07-28 0:06 ` Namhyung Kim
2014-07-28 11:11 ` Thomas Ilsche [this message]
2014-07-29 6:38 ` Namhyung Kim
2014-07-25 7:23 ` [PATCH 1/2] perf tools: Fix make PYTHON override Thomas Ilsche
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=53D62FC9.2010404@tu-dresden.de \
--to=thomas.ilsche@tu-dresden.de \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--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 \
/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