Your message dated Thu, 4 Sep 2025 22:19:39 +0000
with message-id
<blapr20mb4226237380e9bf682e2d7822d6...@blapr20mb4226.namprd20.prod.outlook.com>
and subject line Re: msolve: ftbfs with GCC-15
has caused the Debian Bug report #1097419,
regarding msolve: ftbfs with GCC-15
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1097419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097419
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:msolve
Version: 0.7.3-1
Severity: important
Tags: sid forky
User: [email protected]
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/msolve_0.7.3-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
[...]
checking whether AVX512-F is supported by the processor... yes
checking whether AVX512-F is supported by the processor and OS... yes
checking whether C compiler accepts -mavx512f... yes
checking whether AVX512-CD is supported by the processor... yes
checking whether AVX512-CD is supported by the processor and OS... yes
checking whether C compiler accepts -mavx512cd... yes
checking whether AVX512-PF is supported by the processor... no
checking whether AVX512-ER is supported by the processor... no
checking whether AVX512-VL is supported by the processor... yes
checking whether AVX512-VL is supported by the processor and OS... yes
checking whether C compiler accepts -mavx512vl... yes
checking whether AVX512-BW is supported by the processor... yes
checking whether AVX512-BW is supported by the processor and OS... yes
checking whether C compiler accepts -mavx512bw... yes
checking whether AVX512-DQ is supported by the processor... yes
checking whether AVX512-DQ is supported by the processor and OS... yes
checking whether C compiler accepts -mavx512dq... yes
checking whether AVX512-IFMA is supported by the processor... no
checking whether AVX512-VBMI is supported by the processor... no
checking for __builtin_constant_p... yes
checking for __builtin_clzll... yes
checking for __builtin_clzl... yes
checking for GNU libc compatible malloc... yes
checking for GNU libc compatible realloc... yes
checking for floor... yes
checking for getdelim... yes
checking for gettimeofday... yes
checking for memmove... yes
checking for memset... yes
checking for pow... yes
checking for sqrt... yes
checking for strchr... yes
checking for strstr... yes
checking for strtol... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating msolve.pc
config.status: creating src/fglm/Makefile
config.status: creating src/neogb/Makefile
config.status: creating src/usolve/Makefile
config.status: creating src/msolve/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
dh_auto_build
make -j8
make[1]: Entering directory '/build/reproducible-path/msolve-0.7.3'
make all-recursive
make[2]: Entering directory '/build/reproducible-path/msolve-0.7.3'
Making all in src/usolve
make[3]: Entering directory '/build/reproducible-path/msolve-0.7.3/src/usolve'
/bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -mmmx -msse -msse2 -msse3 -mssse3
-msse4.1 -msse4.2 -maes -mavx -mfma -mavx2 -mavx512f -mavx512cd -mavx512vl
-mavx512bw -mavx512dq -mrdrnd -mbmi -mbmi2 -madx -mabm -fopenmp -g -O2
-Werror=implicit-function-declaration
-ffile-prefix-map=/build/reproducible-path/msolve-0.7.3=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -c -o libusolve_la-usolve.lo `test -f
'usolve.c' || echo './'`usolve.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time
-D_FORTIFY_SOURCE=2 -mmmx -msse -msse2 -msse3 -mssse3 -msse4.1 -msse4.2 -maes
-mavx -mfma -mavx2 -mavx512f -mavx512cd -mavx512vl -mavx512bw -mavx512dq
-mrdrnd -mbmi -mbmi2 -madx -mabm -fopenmp -g -O2
-Werror=implicit-function-declaration
-ffile-prefix-map=/build/reproducible-path/msolve-0.7.3=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -c usolve.c -fPIC -DPIC -o
.libs/libusolve_la-usolve.o
In file included from usolve.c:35:
/usr/include/flint/flint.h:241:16: error: expected ';' before 'void'
241 | FLINT_NORETURN void flint_abort(void);
| ^~~~
/usr/include/flint/flint.h:484:16: error: expected ';' before 'void'
484 | FLINT_NORETURN void flint_throw(flint_err_t exc, const char * msg, ...);
| ^~~~
make[3]: *** [Makefile:453: libusolve_la-usolve.lo] Error 1
make[3]: Leaving directory '/build/reproducible-path/msolve-0.7.3/src/usolve'
make[2]: *** [Makefile:1260: all-recursive] Error 1
make[2]: Leaving directory '/build/reproducible-path/msolve-0.7.3'
make[1]: *** [Makefile:1011: all] Error 2
make[1]: Leaving directory '/build/reproducible-path/msolve-0.7.3'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:9: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
On Tue, 18 Feb 2025 22:20:01 +0000 "Torrance, Douglas" <[email protected]>
wrote:
> This should be fixed when #1096641 [1] is fixed, which should be after the
> next upstream release of FLINT.
FLINT 3.3.1 was just uploaded to unstable with the fix, and msolve is now
building successfully with GCC 15. See for example
https://buildd.debian.org/status/fetch.php?pkg=flint&arch=all&ver=3.3.1-1&stamp=1756912148&raw=0
Closing
--- End Message ---
