Re: [patch] use python-config if available

[Doug Evans <dje@google.com>]

On Thu, Dec 20, 2012 at 11:57 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>> cross building in a multiarch environment, where the host libraries
>> are installed, and a <host>-python-config is shipped as part of the
>> system python.  This <host>-python-config is a backport of
>> http://bugs.python.org/issue16235 (not yet applied upstream).
>
> Ah, OK. Now I understand your problem.
>
>> so what is your recommendation? configure.ac reads:
>>
>> dnl /path/to/python/executable -
>> dnl        Run python-config.py with this version of python to fetch the
>> dnl        compilation parameters.
>> dnl        NOTE: This needn't be the real python executable.
>> dnl        In a cross-compilation scenario (build != host), this could be
>> dnl        a shell script that provides what python-config.py provides for
>> dnl        --ldflags, --includes, --exec-prefix.
>>
>> do I really have to provide a shell script, which shifts the first
>> parameter, and then calls the real python-config?
>
> I think that this was the plan, yes; but Doug Evans would probably
> know more, as he is the main author of this code (I only fiddled
> with it).

The patch is fine with me.
[The plan wasn't to shift and call the "real" python-config ... at the
time there was no real python-config for cross builds.]

One typo: should be ${python_config}

-        AC_ERROR(failure running python-config --exec-prefix)
+        AC_ERROR(failure running ${python-config} --exec-prefix)