From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= Subject: Re: "./configure: line 7058: python-config: command not found" after commit 0013245 Date: Thu, 5 Mar 2015 09:32:58 +0100 Message-ID: <54F814BA.7070900@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> <1425485640.25940.183.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YTRDm-0001kF-Iq for xen-devel@lists.xenproject.org; Thu, 05 Mar 2015 08:33:30 +0000 In-Reply-To: <1425485640.25940.183.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell , Ian Jackson Cc: xen-devel , Julien Grall , Wei Liu List-Id: xen-devel@lists.xenproject.org El 04/03/15 a les 17.14, Ian Campbell ha escrit: > 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. Same here, I thought configure was failing. > So it sounds like perhaps all that is needed is some judicious use of > "2>/dev/null"? But we still require python-config for python versions >= 2.5, or else we will fail to detect if the workaround is needed? Roger.