Bug#1096515: deal.ii: ftbfs with GCC-15

[Matthias Klose]

Package: src:deal.ii
Version: 9.6.2-1
Severity: important
Tags: sid forky
User: debian-gcc at lists.debian.org
Usertags: ftbfs-gcc-15

[This bug is NOT targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-15/g++-15, but succeeds to build with gcc-14/g++-14. The
severity of this report will be raised before the forky release.

The full build log can be found at:
http://qa-logs.debian.net/2025/02/16/amd64exp/deal.ii_9.6.2-1_unstable_gccexp.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 15, either set CC=gcc-15 CXX=g++-15 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

GCC 15 now defaults to the C23/C++23 standards, exposing many FTBFS.
Other Common build failures are new warnings resulting in build failures
with -Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-15/porting_to.html

[...]
220/234 Test  #98: examples/step-45.mpirun=2.release ...........................   Passed  142.69 sec
        Start 124: examples/step-55.mpirun=2.release
221/234 Test #124: examples/step-55.mpirun=2.release ...........................   Passed    8.82 sec
        Start 142: examples/step-64.mpirun=2.debug
222/234 Test  #96: examples/step-45.mpirun=2.debug .............................   Passed  173.58 sec
        Start 144: examples/step-64.mpirun=2.release
223/234 Test #144: examples/step-64.mpirun=2.release ...........................   Passed    8.67 sec
        Start 184: examples/step-89.mpirun=2.debug
224/234 Test #184: examples/step-89.mpirun=2.debug .............................   Passed   10.72 sec
        Start 186: examples/step-89.mpirun=2.release
225/234 Test #186: examples/step-89.mpirun=2.release ...........................   Passed    2.52 sec
        Start 208: quick_tests/mpi.mpirun=2.debug
226/234 Test #208: quick_tests/mpi.mpirun=2.debug ..............................   Passed    1.33 sec
        Start 210: quick_tests/mpi.mpirun=2.release
227/234 Test #210: quick_tests/mpi.mpirun=2.release ............................   Passed    1.22 sec
        Start 218: quick_tests/step-metis.mpirun=2.debug
228/234 Test #218: quick_tests/step-metis.mpirun=2.debug .......................   Passed    1.33 sec
        Start 220: quick_tests/step-metis.mpirun=2.release
229/234 Test #220: quick_tests/step-metis.mpirun=2.release .....................   Passed    1.25 sec
230/234 Test #122: examples/step-55.mpirun=2.debug .............................   Passed  118.97 sec
231/234 Test #142: examples/step-64.mpirun=2.debug .............................   Passed  105.33 sec
232/234 Test  #20: examples/step-18.mpirun=2.debug .............................   Passed  441.79 sec
        Start 212: quick_tests/p4est.mpirun=10.debug
233/234 Test #212: quick_tests/p4est.mpirun=10.debug ...........................   Passed    1.98 sec
        Start 214: quick_tests/p4est.mpirun=10.release
234/234 Test #214: quick_tests/p4est.mpirun=10.release .........................   Passed    1.43 sec

99% tests passed, 1 tests failed out of 234

Total Test time (real) = 4541.53 sec

The following tests FAILED:
	 11 - examples/step-14.debug (Timeout)
Errors while running CTest

**************************************************************************
**                                                                      **
**                Error: Some of the quick tests failed.                **
**                                                                      **
**************************************************************************

Check the terminal output above. You can run all failing quick tests again
via  $ ctest --rerun-failed --output-on-failure -R quick_tests/

If you need help with this problem, open a bug report on the issue tracker

               https://github.com/dealii/dealii/issues/new

or write to the mailing list linked at https://www.dealii.org/mail.html
Please also add the files quick_tests.log , Testing/Temporary/LastTest.log
to your bug report.


CMake Error at /build/reproducible-path/deal.ii-9.6.2/tests/run_quick_tests.cmake:110 (message):
  quick tests failed


make[5]: *** [tests/CMakeFiles/test.dir/build.make:74: tests/CMakeFiles/test] Error 1
make[5]: Leaving directory '/build/reproducible-path/deal.ii-9.6.2/obj-x86_64-linux-gnu'
make[4]: *** [CMakeFiles/Makefile2:7560: tests/CMakeFiles/test.dir/all] Error 2
make[4]: Leaving directory '/build/reproducible-path/deal.ii-9.6.2/obj-x86_64-linux-gnu'
make[3]: *** [CMakeFiles/Makefile2:7567: tests/CMakeFiles/test.dir/rule] Error 2
make[3]: Leaving directory '/build/reproducible-path/deal.ii-9.6.2/obj-x86_64-linux-gnu'
make[2]: *** [Makefile:2616: test] Error 2
make[2]: Leaving directory '/build/reproducible-path/deal.ii-9.6.2/obj-x86_64-linux-gnu'
dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=--verbose ARGS\+=-j1 returned exit code 2
make[1]: *** [debian/rules:69: override_dh_auto_test] Error 25
make[1]: Leaving directory '/build/reproducible-path/deal.ii-9.6.2'
make: *** [debian/rules:11: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2