[Spice-devel] [PATCH 7/7] Use found python binary to check for pyparsing
Hans de Goede
hdegoede at redhat.com
Fri Jan 20 00:56:24 PST 2012
Looks good, ACK.
Regards,
Hans
On 01/19/2012 09:10 PM, Dan McGee wrote:
> This matches what we do in client/Makefile.am to actually run the
> python scripts, which is to use the python binary we find first,
> preferring 'python2' over 'python'. This makes the compile work on odd
> systems such as Arch Linux where the python binary is actually python3.
>
> Signed-off-by: Dan McGee<dpmcgee at gmail.com>
> ---
> configure.ac | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/configure.ac b/configure.ac
> index da60017..b6fb751 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -217,7 +217,7 @@ SPICE_REQUIRES+=" celt051>= 0.5.1.1"
>
> if test ! -e client/generated_marshallers.cpp; then
> AC_MSG_CHECKING([for pyparsing python module])
> -echo "import pyparsing" | python ->/dev/null 2>&1
> +echo "import pyparsing" | ${PYTHON} ->/dev/null 2>&1
> if test $? -ne 0 ; then
> AC_MSG_RESULT([not found])
> AC_MSG_ERROR([pyparsing python module is required to compile this package])
> @@ -531,6 +531,7 @@ echo "
> prefix: ${prefix}
> c compiler: ${CC}
> c++ compiler: ${CXX}
> + python: ${PYTHON}
>
> Build Spice client: ${enable_client}
>
More information about the Spice-devel
mailing list