Bug#935752: gcc-9-cross-mipsen: FTBFS (/usr/bin/python: bad interpreter: No such file or directory)

[Santiago Vila <sanvila@debian.org>]

Package: src:gcc-9-cross-mipsen
Version: 1+c1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:

--------------------------------------------------------------------------------
[...]
 debian/rules build-indep
gcc: 9.2.1-3 / 9.1.0-10cross1

old gcc version: 9.1.0-10 / 1

new gcc version: 9.2.1-3cross1
START stamp-dir/init-gcc
mkdir -p gcc
set -ex; \
cd gcc ; \
ln -sf /usr/src/gcc-9/gcc-9.2.0-dfsg.tar.xz gcc-9.2.0-dfsg.tar.xz ;\
cp -a  /usr/src/gcc-9/debian/ . ; \
if [ -n "$(grep -v '^\#' /<<PKGBUILDDIR>>/debian/patches/gcc-9/series)" ]; then \
  QUILT_PATCHES=/<<PKGBUILDDIR>>/debian/patches/gcc-9 quilt push --quiltrc /dev/null -a ; \
fi

[ ... ]

if [ xinfo = xinfo ]; then \
  rm -f doc/gfc-internals.info-*; \
  makeinfo --split-size=5000000 --split-size=5000000 -I ../../src/gcc/doc/include -I ../../src/gcc/fortran \
    -o doc/gfc-internals.info ../../src/gcc/fortran/gfc-internals.texi; \
else true; fi
../../src/gcc/fortran/gfc-internals.texi: warning: document without nodes
mkdir -p gm2/images
if [ -f ../../src/gcc/gm2/images/gnu.eps ] ; then \
           cp ../../src/gcc/gm2/images/gnu.eps /<<PKGBUILDDIR>>/gcc/build/gcc/gm2/images/gnu.eps ; \
        else \
           pngtopnm ../../src/gcc/gm2/images/gnupng | pnmtops -noturn > /<<PKGBUILDDIR>>/gcc/build/gcc/gm2/images/gnu.eps ; \
        fi
bash ../../src/gcc/gm2/tools-src/makeSystem -fpim \
             ../../src/gcc/gm2/gm2-libs/SYSTEM.def \
             ../../src/gcc/gm2/gm2-libs/SYSTEM.mod \
             -I../../src/gcc/gm2/gm2-libs \
             "/<<PKGBUILDDIR>>/gcc/build/./gcc/xgm2 -B/<<PKGBUILDDIR>>/gcc/build/./gcc/" /<<PKGBUILDDIR>>/gcc/build/gcc/gm2/gm2-libs/SYSTEM.def
../../src/gcc/gm2/tools-src/def2texi.py -b/<<PKGBUILDDIR>>/gcc/build/gcc/gm2 -f/<<PKGBUILDDIR>>/gcc/build/gcc/gm2/gm2-libs/SYSTEM.def > /<<PKGBUILDDIR>>/gcc/build/gcc/gm2/SYSTEM-pim.texi
/bin/bash: ../../src/gcc/gm2/tools-src/def2texi.py: /usr/bin/python: bad interpreter: No such file or directory
make[5]: *** [../../src/gcc/gm2/Make-lang.in:247: gm2/SYSTEM-pim.texi] Error 126
make[5]: Leaving directory '/<<PKGBUILDDIR>>/gcc/build/gcc'
make[4]: *** [Makefile:4368: all-gcc] Error 2
make[4]: Leaving directory '/<<PKGBUILDDIR>>/gcc/build'
make[3]: *** [Makefile:970: all] Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>/gcc/build'
TTTTT Thu, 22 Aug 2019 13:25:38 +0000

[ ... ]

make[2]: *** [debian/rules2:1230: stamps/05-build-stamp] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>/gcc'
make[1]: *** [debian/rules:40: build] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>/gcc'
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
make: *** [debian/rules:410: stamp-dir/build-gcc.mips64] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2
--------------------------------------------------------------------------------

The build was made in my autobuilder with "dpkg-buildpackage -A". I guess it will
happen 100% of the time when built in a clean chroot.

If this is really a bug in one of the build-depends, please use reassign and affects,
so that this is still visible in the BTS web page for this package.

Thanks.