automake-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FYI: python checking message fix (Was: Re: Bug#157778: automake1.6: mino


From: Alexandre Duret-Lutz
Subject: FYI: python checking message fix (Was: Re: Bug#157778: automake1.6: minor problem with python support)
Date: 24 Aug 2002 14:34:20 +0200
User-agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7

>>> "Jochen" == Jochen Voss <address@hidden> writes:

 Jochen> Package: automake1.6
 Jochen> Version: 1.6.3-1
 Jochen> Severity: minor
 Jochen> File: /usr/share/aclocal-1.6/python.m4

 Jochen> Hello,

 Jochen> there is a minor problem with the python support
 Jochen> of automake.  Under some conditions the output of
 Jochen> AM_PATH_PYTHON uses some undefined variables:

 Jochen> I have a AM_PATH_PYTHON on a single line in my configure.ac
 Jochen> file, i.e. I do not check for a specific version of Python.
 Jochen> The output of the generated configure script is

 Jochen> checking for python... /usr/bin/python
 Jochen> checking for  version... 2.1
 Jochen> checking for  platform... linux2
 Jochen>             ^^^
 Jochen> something is missing here!

Thanks!  I'm installing the following patch on CVS Automake.
This will appear in Automake 1.7.

2002-08-24  Alexandre Duret-Lutz  <address@hidden>

        For Debian Bug#157778:
        * m4/python.m4: Fix output of `python' in checking messages
        when no version of Python is required.

Index: m4/python.m4
===================================================================
RCS file: /cvs/automake/automake/m4/python.m4,v
retrieving revision 1.8
diff -u -r1.8 python.m4
--- m4/python.m4        8 Jan 2002 18:03:36 -0000       1.8
+++ m4/python.m4        24 Aug 2002 12:41:18 -0000
@@ -56,7 +56,9 @@
   m4_if([$1],[],[
     dnl No version check is needed.
     # Find any Python interpreter.
-    AC_PATH_PROG([PYTHON], _AM_PYTHON_INTERPRETER_LIST)],[
+    AC_PATH_PROG([PYTHON], _AM_PYTHON_INTERPRETER_LIST)
+    am_display_PYTHON=python
+  ], [
     dnl A version check is needed.
     if test -n "$PYTHON"; then
       # If the user set $PYTHON, use it and don't search something else.
@@ -77,6 +79,7 @@
         done])
       # Set $PYTHON to the absolute path of $am_cv_pathless_PYTHON.
       AC_PATH_PROG([PYTHON], [$am_cv_pathless_PYTHON])
+      am_display_PYTHON=$am_cv_pathless_PYTHON
     fi
   ])
 
@@ -84,7 +87,7 @@
   dnl the best way to do this; it's what "site.py" does in the standard
   dnl library.
 
-  AC_CACHE_CHECK([for $am_cv_pathless_PYTHON version], [am_cv_python_version],
+  AC_CACHE_CHECK([for $am_display_PYTHON version], [am_cv_python_version],
     [am_cv_python_version=`$PYTHON -c "import sys; print sys.version[[:3]]"`])
   AC_SUBST([PYTHON_VERSION], [$am_cv_python_version])
 
@@ -99,8 +102,7 @@
   dnl At times (like when building shared libraries) you may want
   dnl to know which OS platform Python thinks this is.
 
-  AC_CACHE_CHECK([for $am_cv_pathless_PYTHON platform],
-                [am_cv_python_platform],
+  AC_CACHE_CHECK([for $am_display_PYTHON platform], [am_cv_python_platform],
     [am_cv_python_platform=`$PYTHON -c "import sys; print sys.platform"`])
   AC_SUBST([PYTHON_PLATFORM], [$am_cv_python_platform])
 

-- 
Alexandre Duret-Lutz





reply via email to

[Prev in Thread] Current Thread [Next in Thread]