Source: gcc-xtensa-lx106 Version: 5 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200222 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > tar xf /usr/src/gcc-9/gcc-9.2.0-dfsg.tar.xz > ln -s gcc-9* gcc-source > cp debian/overlay/include/xtensa-config.h gcc-source/include/ > mkdir -p debian/stamp > cp /usr/share/doc/gcc-9-source/copyright debian/copyright-gcc > touch debian/stamp/tar > set -ex; \ > cd /<<PKGBUILDDIR>>/gcc-source; \ > for patch in svn-updates.diff; do \ > echo Applying patch "$patch"; \ > patch -p2 < /usr/src/gcc-9/patches/$patch; \ > done > + cd /<<PKGBUILDDIR>>/gcc-source > + echo Applying patch svn-updates.diff > Applying patch svn-updates.diff > /bin/sh: 5: cannot open /usr/src/gcc-9/patches/svn-updates.diff: No such file > + patch -p2 > make[1]: *** [debian/rules:89: debian/stamp/unpack] Error 2 The full build log is available from: http://qa-logs.debian.net/2020/02/22/gcc-xtensa-lx106_5_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.