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.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
