From: Michael Witten <mfwitten@gmail.com>
To: David Ahern <dsahern@gmail.com>
Cc: Pekka Enberg <penberg@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Ingo Molnar <mingo@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PROBLEM] perf requires python-devel to compile
Date: Tue, 16 Apr 2013 20:41:59 -0000 [thread overview]
Message-ID: <516dba78.8695320a.583d.0722@mx.google.com> (raw)
In-Reply-To: <516DB548.7010703@gmail.com>
On Tue, 16 Apr 2013 13:32:08 -0700, David Ahern wrote:
> On 4/16/13 10:08 AM, Michael Witten wrote:
>> You should probably disable python support more directly:
>>
>> make NO_LIBPYTHON=1
>
> sure, but I should not have to do anything. The intent of the existing
> auto-probing code is to figure out what is installed and build a binary
> with those capabilities. In this case not having python installed causes
> it to blow up.
That's certainly how it behaved up until the regression.
To make matters worse, the NO_LIBPYTHON variable is checked only *after*
probing for an executable `python'; in the case that no python is installed
at all, the workaround is to double up on your current trick:
make PYTHON=false PYTHON_CONFIG=false
next prev parent reply other threads:[~2013-04-16 20:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 10:58 [PROBLEM] perf requires python-devel to compile Pekka Enberg
2013-04-16 2:14 ` Namhyung Kim
2013-04-16 4:26 ` David Ahern
2013-04-16 17:08 ` Michael Witten
2013-04-16 20:32 ` David Ahern
2013-04-16 20:41 ` Michael Witten [this message]
2013-04-17 2:23 ` [PATCH] perf tools: Revert regression in configuration of Python support Michael Witten
2013-04-16 17:16 ` [PROBLEM] perf requires python-devel to compile Pekka Enberg
2013-07-12 8:52 ` [tip:perf/urgent] perf tools: Revert regression in configuration of Python support tip-bot for Michael Witten
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=516dba78.8695320a.583d.0722@mx.google.com \
--to=mfwitten@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=penberg@kernel.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