./configure without python3?

Martin Schwenke martin at meltin.net
Mon Dec 10 22:08:12 UTC 2018

Unfortunately, I haven't been following the python3 changes closely, so
a quick question...

Last night all of our local CI jobs fell over because python3 was not
found in ./configure:

  ${PYTHON:=python3} $WAF configure "$@" || exit 1

None of our jobs set $PYTHON.

I just wanted to check that we really want ./configure to fall over
when python3 is not available, rather than falling back to python[2],
as in:

  if [ -z "$PYTHON" ] ; then
    if type python3 >/dev/null 2>&1 ; then
      export PYTHON="python3"
    elif type python >/dev/null 2>&1 ; then
      export PYTHON="python"
      echo "$0: error, can't find python3 or python"
      exit 1
  $WAF configure "$@" || exit 1


peace & happiness,

More information about the samba-technical mailing list