Bug#1017284: fenics-dolfinx: FTBFS: CheckSymbolExists.c:8:19: error: ‘PETSC_USE_COMPLEX’ undeclared (first use in this function); did you mean ‘PETSC_HAVE_COMPLEX’?

[Lucas Nussbaum]

Source: fenics-dolfinx
Version: 1:0.4.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas at debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/cc  -I/usr/lib/petscdir/petsc3.16/x86_64-linux-gnu-real/include -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Wdate-time -D_FORTIFY_SOURCE=2  -o CMakeFiles/cmTC_d1fc9.dir/CheckSymbolExists.c.o -c /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu-real/CMakeFiles/CMakeTmp/CheckSymbolExists.c
> /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu-real/CMakeFiles/CMakeTmp/CheckSymbolExists.c: In function ‘main’:
> /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu-real/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:19: error: ‘PETSC_USE_COMPLEX’ undeclared (first use in this function); did you mean ‘PETSC_HAVE_COMPLEX’?
>     8 |   return ((int*)(&PETSC_USE_COMPLEX))[argc];
>       |                   ^~~~~~~~~~~~~~~~~
>       |                   PETSC_HAVE_COMPLEX
> /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu-real/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:19: note: each undeclared identifier is reported only once for each function it appears in
> gmake[3]: *** [CMakeFiles/cmTC_d1fc9.dir/build.make:78: CMakeFiles/cmTC_d1fc9.dir/CheckSymbolExists.c.o] Error 1
> gmake[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu-real/CMakeFiles/CMakeTmp'
> gmake[2]: *** [Makefile:127: cmTC_d1fc9/fast] Error 2
> gmake[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu-real/CMakeFiles/CMakeTmp'
> 
> 
> File /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu-real/CMakeFiles/CMakeTmp/CheckSymbolExists.c:
> /* */
> #include <petscsystypes.h>
> 
> int main(int argc, char** argv)
> {
>   (void)argv;
> #ifndef PETSC_USE_COMPLEX
>   return ((int*)(&PETSC_USE_COMPLEX))[argc];
> #else
>   (void)argc;
>   return 0;
> #endif
> }
> dh_auto_configure: error: cd obj-x86_64-linux-gnu-real && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -D CMAKE_BUILD_TYPE:STRING=RelWithDebInfo -D BUILD_SHARED_LIBS:BOOL=ON -D CMAKE_SKIP_RPATH:BOOL=ON -D CMAKE_INSTALL_RPATH_USE_LINK_PATH:BOOL=OFF -D DOLFINX_ENABLE_TRILINOS:BOOL=OFF -D DOLFINX_ENABLE_HDF5:BOOL=ON -D HDF5_C_COMPILER_EXECUTABLE:FILEPATH=/usr/bin/h5pcc -D DOLFINX_ENABLE_PARMETIS:BOOL=OFF -D DOLFINX_ENABLE_SCOTCH:BOOL=ON -D DOLFINX_ENABLE_DOCS:BOOL=OFF -D DOLFINX_ENABLE_MPI:BOOL=ON -D MPIEXEC_PARAMS:STRING=--oversubscribe -D CMAKE_CXX_FLAGS:STRING=-fpermissive -D "DOLFINX_EXTRA_CXX_FLAGS:STRING=-g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security" -DXTENSOR_USE_XSIMD=ON /<<PKGBUILDDIR>>/cpp .. returned exit code 1
> make[1]: *** [debian/rules:144: override_dh_auto_configure] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/fenics-dolfinx_0.4.1-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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.