Bug#986523: odb: FTBFS: i386.h:2500:10: fatal error: common/config/i386/i386-cpuinfo.h: No such file or directory
On Wed, Apr 14, 2021 at 9:18 PM Andreas Beckmann wrote: > On Wed, 7 Apr 2021 08:32:20 +0200 Lucas Nussbaum wrote: > > > /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 > > This is fixed in gcc-10 10.3 in experimental, according to doko the > workaround is to build with g++-9 for bullseye. (#986519) Meaning GCC 10 is still broken on amd64, its gcc-10-plugin-dev has a regression for Bullseye over GCC 9. But OK, not my business. Will build odb with GCC 9. Regards, Laszlo/GCS
Bug#986523: odb: FTBFS: i386.h:2500:10: fatal error: common/config/i386/i386-cpuinfo.h: No such file or directory
Control: tag -1 patch On Wed, 7 Apr 2021 08:32:20 +0200 Lucas Nussbaum wrote: > /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 This is fixed in gcc-10 10.3 in experimental, according to doko the workaround is to build with g++-9 for bullseye. (#986519) Andreas diff -Nru odb-2.4.0/debian/control odb-2.4.0/debian/control --- odb-2.4.0/debian/control 2020-07-26 14:47:04.0 +0200 +++ odb-2.4.0/debian/control 2021-04-14 21:03:41.0 +0200 @@ -2,7 +2,7 @@ Section: devel Priority: optional Maintainer: Laszlo Boszormenyi (GCS) -Build-Depends: debhelper-compat (= 11), g++ (>= 4:10), gcc-10-plugin-dev, libexpat1-dev, libcutl-dev +Build-Depends: debhelper-compat (= 11), g++-9, gcc-9-plugin-dev, libexpat1-dev, libcutl-dev Standards-Version: 4.5.0 Homepage: https://www.codesynthesis.com/products/odb diff -Nru odb-2.4.0/debian/rules odb-2.4.0/debian/rules --- odb-2.4.0/debian/rules 2018-12-06 15:54:26.0 +0100 +++ odb-2.4.0/debian/rules 2021-04-14 21:03:41.0 +0200 @@ -1,6 +1,9 @@ #!/usr/bin/make -f # -*- makefile -*- +export CC=gcc-9 +export CXX=g++-9 + # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1
Bug#986523: odb: FTBFS: i386.h:2500:10: fatal error: common/config/i386/i386-cpuinfo.h: No such file or directory
Source: odb Version: 2.4.0-13 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210406 ftbfs-bullseye Hi, During a rebuild of all packages in bullseye, 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=/<>=. -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=/<>=. > -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/04/06/odb_2.4.0-13_testing.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 mine 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.
