Source: odb Version: 2.4.0-13 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I'..' > -I'..' -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/lib/gcc/x86_64-linux-gnu/10/plugin/include -std=c++0x -g -O2 > -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat > -Werror=format-security -fno-devirtualize -c -o cxx-lexer.lo cxx-lexer.cxx > libtool: compile: g++ -DHAVE_CONFIG_H -I.. -I.. -Wdate-time > -D_FORTIFY_SOURCE=2 -I/usr/lib/gcc/x86_64-linux-gnu/10/plugin/include > -std=c++0x -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -fno-devirtualize > -c cxx-lexer.cxx -fPIC -DPIC -o .libs/cxx-lexer.o > In file included from /usr/lib/gcc/x86_64-linux-gnu/10/plugin/include/tm.h:26, > from > /usr/lib/gcc/x86_64-linux-gnu/10/plugin/include/backend.h:28, > from > /usr/lib/gcc/x86_64-linux-gnu/10/plugin/include/gcc-plugin.h:30, > from ../odb/gcc.hxx:48, > from cxx-lexer.cxx:5: > /usr/lib/gcc/x86_64-linux-gnu/10/plugin/include/config/i386/i386.h:2500:10: > fatal error: common/config/i386/i386-cpuinfo.h: No such file or directory > 2500 | #include "common/config/i386/i386-cpuinfo.h" > | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > compilation terminated. > make[3]: *** [Makefile:1143: cxx-lexer.lo] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/01/20/odb_2.4.0-13_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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. 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.
