In the configure check for the Python distutils module, use a less obscure

shell construct to hide away the stderr output.  Python 3.1 actually core
dumps on the current invocation (http://bugs.python.org/issue7111), but the
new version also has the more general advantage of saving the error message
in config.log for analysis.

config/python.m4

@@ -1,7 +1,7 @@
 #
 # Autoconf macros for configuring the build of Python extension modules
 #
-# $PostgreSQL: pgsql/config/python.m4,v 1.15 2009/01/04 00:54:15 petere Exp $
+# $PostgreSQL: pgsql/config/python.m4,v 1.16 2009/10/14 21:59:15 petere Exp $
 #
 
 # PGAC_PATH_PYTHON
@@ -22,7 +22,7 @@ fi
 AC_DEFUN([_PGAC_CHECK_PYTHON_DIRS],
 [AC_REQUIRE([PGAC_PATH_PYTHON])
 AC_MSG_CHECKING([for Python distutils module])
-if "${PYTHON}" 2>&- -c 'import distutils'
+if "${PYTHON}" -c 'import distutils' 2>&AS_MESSAGE_LOG_FD
 then
     AC_MSG_RESULT(yes)
 else

configure

@@ -7011,7 +7011,7 @@ fi
 
 { $as_echo "$as_me:$LINENO: checking for Python distutils module" >&5
 $as_echo_n "checking for Python distutils module... " >&6; }
-if "${PYTHON}" 2>&- -c 'import distutils'
+if "${PYTHON}" -c 'import distutils' 2>&5
 then
     { $as_echo "$as_me:$LINENO: result: yes" >&5
 $as_echo "yes" >&6; }