From: Ian Campbell <ian.campbell@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Julien Grall <julien.grall@linaro.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: "./configure: line 7058: python-config: command not found" after commit 0013245
Date: Thu, 5 Mar 2015 10:56:50 +0000 [thread overview]
Message-ID: <1425553010.25940.214.camel@citrix.com> (raw)
In-Reply-To: <54F814BA.7070900@citrix.com>
On Thu, 2015-03-05 at 09:32 +0100, Roger Pau Monné wrote:
> > 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?
I've said it a few times in this thread: Until we know that there are
systems which both lack python-config _and_ suffer from the fortify
incompatibility then we can live with this IMHO.
IOW I think we can just assume that the fortify incompatibility is a
feature of either newer distros and/or newer versions of python
implementing hardening flags which is something which has been going on
over the last few years.
Python 2.5 dates back to 2006, before then I think enabling fortify by
default was not all that common.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-03-05 10:56 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 [this message]
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=1425553010.25940.214.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.