From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: "./configure: line 7058: python-config: command not found" after commit 0013245
Date: Tue, 3 Mar 2015 17:36:13 +0000 [thread overview]
Message-ID: <1425404173.25940.82.camel@citrix.com> (raw)
In-Reply-To: <54F5EDDF.3050600@linaro.org>
On Tue, 2015-03-03 at 17:22 +0000, Julien Grall wrote:
> Hi,
>
> I've tried to use ./configure on the latest master and got the below error:
>
> checking for python-config... no
> checking Python.h usability... yes
> checking Python.h presence... yes
> checking for Python.h... yes
> checking for PyArg_ParseTuple in -lpython2.7... yes
> checking whether Python setup.py brokenly enables -D_FORTIFY_SOURCE...
> ./configure: line 7058: python-config: command not found
> no
> checking for xgettext... /usr/bin/xgettext
>
> Shall we require python-config installed on the build-platform?
m4/python_devel.m4 seems to suggest it was made optional on purpose, I
don't know why or which versions of Python were the first to include the
tool though.
Perhaps AX_CHECK_PYTHON_FORTIFY_NOOPT should be a nop unless
python-config is available?
Or perhaps AX_CHECK_PYTHON_DEVEL should export PYTHON_CFLAGS etc which
the fortify test should look at instead of invoking python-cofnig?
Ian.
prev parent reply other threads:[~2015-03-03 17:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 17:22 "./configure: line 7058: python-config: command not found" after commit 0013245 Julien Grall
2015-03-03 17:36 ` Wei Liu
2015-03-03 17:46 ` Julien Grall
2015-03-03 18:48 ` Wei Liu
2015-03-03 19:41 ` Julien Grall
2015-03-04 9:07 ` Ian Campbell
2015-03-04 12:27 ` Julien Grall
2015-03-04 12:35 ` Ian Campbell
2015-03-04 12:47 ` Julien Grall
2015-03-04 13:00 ` Ian Campbell
2015-03-04 14:02 ` Roger Pau Monné
2015-03-04 14:10 ` Ian Campbell
2015-03-04 16:07 ` Ian Jackson
2015-03-04 16:14 ` Ian Campbell
2015-03-05 8:32 ` Roger Pau Monné
2015-03-05 10:56 ` Ian Campbell
2015-03-03 17:36 ` Ian Campbell [this message]
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=1425404173.25940.82.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@linaro.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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.