From: Ian Campbell <ian.campbell@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
Julien Grall <julien.grall@linaro.org>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: "./configure: line 7058: python-config: command not found" after commit 0013245
Date: Wed, 4 Mar 2015 14:10:18 +0000 [thread overview]
Message-ID: <1425478218.25940.173.camel@citrix.com> (raw)
In-Reply-To: <54F7108B.1020505@citrix.com>
On Wed, 2015-03-04 at 15:02 +0100, Roger Pau Monné wrote:
> Yes, I think so, for python versions > 2.4 we should require
> python-config.
ACK.
> IMHO python_fortify_noopt.m4 should also be fixed to deal
> with older python version that don't have python-config.
That would be ideal, but unless someone shows me/us a system with Python
<=2.4 which suffers from this issue I'd also be inclined to accept a
patch which made that check only apply iff python-config was found
(assuming that would be simpler. it might actually be harder...).
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-03-04 14:10 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 [this message]
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
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=1425478218.25940.173.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@linaro.org \
--cc=roger.pau@citrix.com \
--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.