From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Al Cooper <alcooperx@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
mingo@infradead.org, Jiri Olsa <jolsa@redhat.com>,
Namhyung Kim <namhyung@gmail.com>,
David Ahern <dsahern@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Build failure when python-devel not installed
Date: Tue, 9 Jul 2013 10:19:26 -0300 [thread overview]
Message-ID: <20130709131926.GA3260@ghostprotocols.net> (raw)
Hi,
While trying to build perf on a freshly installed Fedora 18
machine I couldn't do it if python-devel isn't installed.
The expected behaviour is for a warning to be emitted and the
build to continue.
I bisected it down to:
commit 31160d7feab786c991780d7f0ce2755a469e0e5e
"perf tools: Fix GNU make v3.80 compatibility issue"
If I revert this changeset, everything works as expected, I get:
config/Makefile:319: The path '/usr/bin/python-config' is not executable.
config/Makefile:323: No python-config tool was found
config/Makefile:323: Python support will not be built
and I get a perf binary with no python support.
When python-devel is not installed and I have the above cset, I
get:
CHK gtk2
CHK -DHAVE_GTK_INFO_BAR
CHK perl
config/Makefile:319: The path '/usr/bin/python-config' is not executable.
config/Makefile:319: *** Please set 'PYTHON_CONFIG' appropriately. Stop.
make: Leaving directory `/home/acme/git/linux/tools/perf'
[acme@sandy linux]$
Can you take a look at this?
Jiri, this brings another situation to be tested on the 'cd
tools/perf ; make -f tools/make' suite: removing/installing packages
needed to build with some feature to check that it just warns the user
that such feature won't be included instead of stopping the build :-)
- Arnaldo
next reply other threads:[~2013-07-09 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 13:19 Arnaldo Carvalho de Melo [this message]
2013-07-09 14:19 ` Build failure when python-devel not installed David Ahern
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=20130709131926.GA3260@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=alcooperx@gmail.com \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@infradead.org \
--cc=namhyung@gmail.com \
--cc=peterz@infradead.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 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.