kc3-lang/automake/t/python-missing.sh

• Show log

  Commit

• Hash : 84e12c32
  Author :
  Date : 2013-05-17T13:45:44
  

  tests: sanitize 'unset' usages
  
  In some shells (e.g., Solaris 10 /bin/ksh, or NetBSD 5.1 /bin/sh),
  "unset VAR" returns a non-zero exit status in case the VAR variable
  is already unset.  This doesn't interact well with our usage of
  "set -e" in the testsuite.  So far, we've avoided spurious failures
  by either explicitly ignoring the exit status from unset:
  
      unset VAR || :
  
  or explicitly ensuring that a variable is set, before trying to
  unset it:
  
      VAR=; unset VAR
  
  But we can do better, by aliasing the 'unset' command to a custom
  function that will take care of these details for us.  This will
  avoid us annoying spurious failures in the future, failures that
  have already bitten us too much times.  For an example, refer to
  commit 'v1.12.2-88-g5b1dae5' of 2012-08-05 (tests: avoid tons of
  spurious failures on NetBSD).
  
  * t/ax/test-lib.sh (_am_unset): New function.
  (unset): New alias to it.
  (_am_exit): Adjust comments.
  * t/ax/am-test-lib.sh: No need to temporary disable the 'errexit'
  shell flag when unsetting variables that are potentially already
  unset.
  (am_process_requirements): Adjust to remove a now-useless
  workaround related to unset.
  * t/aclocal-macrodir.tap: Likewise.
  * t/aclocal-macrodirs.tap: Likewise.
  * t/auxdir-autodetect.sh: Likewise.
  * t/ax/am-test-lib.sh: Likewise.
  * t/ax/test-lib.sh: Likewise.
  * t/check-tests-in-builddir.sh: Likewise.
  * t/dist-formats.tap: Likewise.
  * t/distcheck-configure-flags-am.sh: Likewise.
  * t/distcheck-configure-flags.sh: Likewise.
  * t/java-empty-classpath.sh: Likewise.
  * t/javaflags.sh: Likewise.
  * t/lflags.sh: Likewise.
  * t/lflags2.sh: Likewise.
  * t/lisp-flags.sh: Likewise.
  * t/lisp6.sh: Likewise.
  * t/missing-auxfile-stops-makefiles-creation.sh: Likewise.
  * t/parallel-am.sh: Likewise.
  * t/parallel-am2.sh: Likewise.
  * t/parallel-am3.sh: Likewise.
  * t/parallel-tests-log-override-recheck.sh: Likewise.
  * t/pkg-config-macros.sh: Likewise.
  * t/python-missing.sh: Likewise.
  * t/python-too-old.sh: Likewise.
  * t/python11.sh: Likewise.
  * t/self-check-dir.tap: Likewise.
  * t/self-check-report.sh: Likewise.
  * t/self-check-seq.tap: Likewise.
  * t/silent-configsite.sh: Likewise.
  * t/suffix6c.sh: Likewise.
  * t/tar-override.sh: Likewise.
  * t/tests-environment-and-log-compiler.sh: Likewise.
  * t/vala-configure.sh: Likewise.
  * t/werror3.sh: Likewise.
  * t/yflags-cmdline-override.sh: Likewise.
  * t/yflags.sh: Likewise.
  * t/yflags2.sh: Likewise.
  
  Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>
  

Download

• t/python-missing.sh

• #! /bin/sh
  # Copyright (C) 2003-2013 Free Software Foundation, Inc.
  #
  # This program is free software; you can redistribute it and/or modify
  # it under the terms of the GNU General Public License as published by
  # the Free Software Foundation; either version 2, or (at your option)
  # any later version.
  #
  # This program is distributed in the hope that it will be useful,
  # but WITHOUT ANY WARRANTY; without even the implied warranty of
  # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  # GNU General Public License for more details.
  #
  # You should have received a copy of the GNU General Public License
  # along with this program.  If not, see <http://www.gnu.org/licenses/>.
  
  # Test detection of missing Python.
  # See also related test t/python-am-path-missing-2.sh (which requires
  # an actual python program).
  
  am_create_testdir=empty
  # An actual python is *not* required in this test.
  . test-init.sh
  
  unset PYTHON
  
  cat > configure.ac <<END
  AC_INIT([$me], [1.0])
  m4_include([mypy.m4])
  AC_OUTPUT
  END
  
  echo AM_PATH_PYTHON > mypy.m4
  
  $ACLOCAL
  $AUTOCONF
  
  # Simulate no Python.
  ./configure PYTHON=: 2>stderr && { cat stderr >&2; exit 1; }
  cat stderr >&2
  grep 'no suitable Python interpreter found' stderr
  
  # Again, but from the environment this time.
  env PYTHON=: ./configure 2>stderr && { cat stderr >&2; exit 1; }
  cat stderr >&2
  grep 'no suitable Python interpreter found' stderr
  
  # Now try using a custom ACTION-IF-NOT-FOUND.
  
  echo 'AM_PATH_PYTHON(,, [echo "$PYTHON" > py])' > mypy.m4
  $AUTOCONF --force
  ./configure PYTHON=:
  test x"$(cat py)" = x:
  
  # Now try requiring a version.
  
  rm -rf autom4te*.cache # Will have to re-run aclocal.
  
  # Hopefully the Python team will never release such a version :-)
  echo 'AM_PATH_PYTHON([9999.9], [])' > mypy.m4
  # The "--force" options (here and below) are truly needed to avoid
  # potential timestamp races.  See automake bug#12210.
  $ACLOCAL --force
  $AUTOCONF --force
  ./configure >stdout 2>stderr && {
    cat stdout
    cat stderr >&2
    exit 1
  }
  cat stdout
  cat stderr >&2
  $EGREP 'checking for a Python interpreter with version >= 9999\.9\.\.\. no(ne)? *$' stdout
  grep 'no suitable Python interpreter found' stderr
  
  # Now try requiring a version and using a custom ACTION-IF-NOT-FOUND.
  
  echo 'AM_PATH_PYTHON([9999.9], [], [echo "$PYTHON" > py])' > mypy.m4
  $AUTOCONF --force
  ./configure
  test x"$(cat py)" = x:
  
  :
  

Download