Source: gdb-mingw-w64 Version: 10.9 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201119 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>>' > set -e; \ > for target in i686-w64-mingw32 x86_64-w64-mingw32; do \ > mkdir -p /<<PKGBUILDDIR>>/build-gdbserver/$target; \ > cd /<<PKGBUILDDIR>>/build-gdbserver/$target; \ > /<<PKGBUILDDIR>>/upstream/gdb/gdbserver/configure \ > --build=x86_64-linux-gnu \ > --host=$target --target=$target \ > --disable-werror \ > CFLAGS="-g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong" > CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2 > -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong" > FCFLAGS="-g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong" > FFLAGS="-g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong" > GCJFLAGS="-g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong" > LDFLAGS="-specs=/usr/share/dpkg/no-pie-link.specs -Xlinker > --no-insert-timestamp -static" OBJCFLAGS="-g -O2 > -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong" > OBJCXXFLAGS="-g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong" ; \ > done > /bin/sh: 5: /<<PKGBUILDDIR>>/upstream/gdb/gdbserver/configure: not found > make[1]: *** [debian/rules:85: override_dh_auto_configure-indep] Error 127 The full build log is available from: http://qa-logs.debian.net/2020/11/19/gdb-mingw-w64_10.9_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.
