All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
	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 09:07:18 +0000	[thread overview]
Message-ID: <1425460038.12103.60.camel@citrix.com> (raw)
In-Reply-To: <54F60E86.2040702@linaro.org>

On Tue, 2015-03-03 at 19:41 +0000, Julien Grall wrote:
> python-dev is not installed. Although I have libpython-dev installed.

And this used to work I suppose?

As I said in <1425404173.25940.82.camel@citrix.com>:

        m4/python_devel.m4 seems to suggest it was made optional on
        purpose, I don't know why or which versions of Python were the
        first to include the tool though.

So it appears to be deliberate that the Python checks do not require
python-config. But the new Python vs. Fortify checks _do_ require it.

So the question is: why was it optional in the first place? Then we
should know if we can make it a requirement or if we need to fix the
Fortify check.

Aha, adding --follow to my earlier git log m4/python_devel.m4 leads me
to:

commit 474a0e59d821bfb49b64c3d722a000bd9b5b7599
Author: Roger Pau Monne <roger.pau@entel.upc.edu>
Date:   Tue Apr 3 14:28:45 2012 +0100

    autoconf: fix python-dev detection on old python versions
    
    Replaced the use of python-config (that is only present in Python >= 2.5.x)
    with the distutils python module.
    
    Signed-off-by: Roger Pau Monne <roger.pau@entel.upc.edu>
    Cc: Zhang, Yang Z <yang.z.zhang@intel.com>
    Tested-by: KUWAMURA Shin'ya <kuwa@jp.fujitsu.com>
    Cc: Ian Campbell <ian.campbell@citrix.com>
    Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>

So it seems like it is necessary to continue to work without
python-config present.

In my same earlier mail I said:
> Perhaps AX_CHECK_PYTHON_FORTIFY_NOOPT should be a nop unless
> python-config is available?
> 
> Or perhaps AX_CHECK_PYTHON_DEVEL should export PYTHON_CFLAGS etc which
> the fortify test should look at instead of invoking python-cofnig?

I think it would be acceptable in the first instance to simply only run
the Fortify check if python-config is present and hope that older
distros didn't have the incompatibility. If we then find such an older
distro then we can look at switching to something more complex.

Can someone cook up a patch please?

Ian.

  reply	other threads:[~2015-03-04  9:07 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 [this message]
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
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=1425460038.12103.60.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=julien.grall@linaro.org \
    --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.