Bug#954497: siconos: FTBFS: cc: error: 654: No such file or directory

Lucas Nussbaum lucas at debian.org
Sun Mar 22 07:31:24 GMT 2020


Source: siconos
Version: 4.2.0+git20181026.0ee5349+dfsg.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/cc   -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DC_HAVE_-diag-disable654 -O3 -DNDEBUG   -diag-disable 654  -o CMakeFiles/cmTC_f69e2.dir/src.c.o   -c /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c
> cc: error: 654: No such file or directory
> make[3]: *** [CMakeFiles/cmTC_f69e2.dir/build.make:66: CMakeFiles/cmTC_f69e2.dir/src.c.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/siconos_4.2.0+git20181026.0ee5349+dfsg.2-2_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.



More information about the debian-science-maintainers mailing list