From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <ian.campbell@citrix.com>
Subject: Re: "./configure: line 7058: python-config: command not
 found" after commit 0013245
Date: Wed, 4 Mar 2015 16:14:00 +0000
Message-ID: <1425485640.25940.183.camel@citrix.com>
References: <54F5EDDF.3050600@linaro.org>
	<20150303173607.GI11855@zion.uk.xensource.com>
	<54F5F360.4040801@linaro.org>
	<20150303184843.GA24803@zion.uk.xensource.com>
	<54F60E86.2040702@linaro.org> <1425460038.12103.60.camel@citrix.com>
	<54F6FA40.3060101@linaro.org> <1425472533.25940.149.camel@citrix.com>
	<54F6FEFC.9060806@linaro.org> <1425474052.25940.152.camel@citrix.com>
	<54F7108B.1020505@citrix.com> <1425478218.25940.173.camel@citrix.com>
	<21751.11714.298738.24191@mariner.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>) id 1YTBwa-0000N1-Eq
	for xen-devel@lists.xenproject.org; Wed, 04 Mar 2015 16:14:44 +0000
In-Reply-To: <21751.11714.298738.24191@mariner.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, Julien Grall <julien.grall@linaro.org>, Wei Liu <wei.liu2@citrix.com>, Roger Pau =?ISO-8859-1?Q?Monn=E9?= <roger.pau@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On Wed, 2015-03-04 at 16:07 +0000, Ian Jackson wrote:
> Ian Campbell writes ("Re: "./configure: line 7058: python-config: command not found" after commit 0013245"):
> > 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...).
> 
> Isn't that what the current code does (rather messily) ?

Yes, I misread Julien's original mail and thought configure was failing
due to the lack of python-config, but you are right, it carries on.

So it sounds like perhaps all that is needed is some judicious use of
"2>/dev/null"?

> 
> That is, it invokes python-config, doesn't notice that python-config
> fails, finds that the no output produced by python-config doesn't
> contain the problematic fortify options, and disables the workaround.
> 
> Ian.