Bug#1097775: rdiff-backup-fs: ftbfs with GCC-15
Package: src:rdiff-backup-fs
Version: 1.0.0-8
Severity: important
Tags: sid forky
User: debian-gcc@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/rdiff-backup-fs_1.0.0-8_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
[...]
../support/gutils.h:16:76: note: in definition of macro ‘debug’
16 | printf("[%s, %d, %s] " format, __FILE__, __LINE__, __FUNCTION__, ##__VA_ARGS__); \
| ^~~~~~~~~~~
necessary.c: In function ‘necessary_get_children’:
necessary.c:201:41: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
201 | debug(1, "retrieved tree %d\n", (int) tree);
| ^
../support/gutils.h:16:76: note: in definition of macro ‘debug’
16 | printf("[%s, %d, %s] " format, __FILE__, __LINE__, __FUNCTION__, ##__VA_ARGS__); \
| ^~~~~~~~~~~
necessary.c: In function ‘build_snapshot’:
necessary.c:372:9: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
372 | write(snapshot_desc, "\n", 1);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
rm -f libstructure.a
ar cr libstructure.a core.o full.o necessary.o support.o
ranlib libstructure.a
make[3]: Leaving directory '/build/reproducible-path/rdiff-backup-fs-1.0.0/structure'
Making all in retriever
make[3]: Entering directory '/build/reproducible-path/rdiff-backup-fs-1.0.0/retriever'
gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/rdiff-backup-fs-1.0.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -g -O3 -I/usr/include/fuse -D_FILE_OFFSET_BITS=64 -c -o retriever.o retriever.c
gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/rdiff-backup-fs-1.0.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -g -O3 -I/usr/include/fuse -D_FILE_OFFSET_BITS=64 -c -o simple.o simple.c
gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/rdiff-backup-fs-1.0.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -g -O3 -I/usr/include/fuse -D_FILE_OFFSET_BITS=64 -c -o support.o support.c
gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/rdiff-backup-fs-1.0.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -g -O3 -I/usr/include/fuse -D_FILE_OFFSET_BITS=64 -c -o limit.o limit.c
simple.c: In function ‘__release_simple’:
simple.c:42:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
42 | if (!node)
| ^~
simple.c:44:9: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
44 | node->count--;
| ^~~~
limit.c: In function ‘release_limit’:
limit.c:47:56: warning: comparison of constant ‘-1’ with boolean expression is always false [-Wbool-compare]
47 | if ((repo == repo_number(fsinfo, stats->path)) == -1)
| ^~
limit.c: In function ‘__retrieve_limit’:
limit.c:98:17: error: too many arguments to function ‘cache_delete’; expected 0, have 1
98 | cache_delete(fsinfo);
| ^~~~~~~~~~~~ ~~~~~~
limit.c:25:5: note: declared here
25 | int cache_delete();
| ^~~~~~~~~~~~
limit.c: At top level:
limit.c:155:5: error: conflicting types for ‘cache_delete’; have ‘int(struct file_system_info *)’
155 | int cache_delete(struct file_system_info *fsinfo){
| ^~~~~~~~~~~~
limit.c:25:5: note: previous declaration of ‘cache_delete’ with type ‘int(void)’
25 | int cache_delete();
| ^~~~~~~~~~~~
limit.c: In function ‘cache_delete’:
limit.c:161:6: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
161 | if ((repo = repo_number(fsinfo, cache->node->path)) == -1)
| ^~
In file included from limit.c:2:
../support/gutils.h:14:35: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
14 | #define debug(level, format, ...) { \
| ^
limit.c:163:9: note: in expansion of macro ‘debug’
163 | debug(3, "Deleting from cache %s file with %d open and %d cached files;\n", cache->node->path, open_count, cache_count);
| ^~~~~
make[3]: *** [Makefile:344: limit.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/build/reproducible-path/rdiff-backup-fs-1.0.0/retriever'
make[2]: *** [Makefile:560: all-recursive] Error 1
make[2]: Leaving directory '/build/reproducible-path/rdiff-backup-fs-1.0.0'
make[1]: *** [Makefile:381: all] Error 2
make[1]: Leaving directory '/build/reproducible-path/rdiff-backup-fs-1.0.0'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:13: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Reply to: