Your message dated Thu, 29 Jan 2026 15:08:04 +0000
with message-id <[email protected]>
and subject line Bug#1096368: fixed in bindfs 1.18.4-0.1
has caused the Debian Bug report #1096368,
regarding bindfs: 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.)
--
1096368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096368
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:bindfs
Version: 1.14.7-1.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/bindfs_1.14.7-1.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 for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for lutimes... yes
checking for utimensat... yes
checking for setxattr... yes
checking for getxattr... yes
checking for listxattr... yes
checking for removexattr... yes
checking for lsetxattr... yes
checking for lgetxattr... yes
checking for llistxattr... yes
checking for lremovexattr... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for fuse... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating tests/Makefile
config.status: creating tests/internals/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
dh_auto_build
dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9
in use)
make -j1
make[1]: Entering directory '/build/reproducible-path/bindfs-1.14.7'
make all-recursive
make[2]: Entering directory '/build/reproducible-path/bindfs-1.14.7'
Making all in src
make[3]: Entering directory '/build/reproducible-path/bindfs-1.14.7/src'
gcc -DHAVE_CONFIG_H -I. -I.. -D_REENTRANT -D_FILE_OFFSET_BITS=64
-DFUSE_USE_VERSION=26 -I/usr/include/fuse -D_FILE_OFFSET_BITS=64 -Wdate-time
-D_FORTIFY_SOURCE=2 -Wall -fno-common -g -O2
-Werror=implicit-function-declaration
-ffile-prefix-map=/build/reproducible-path/bindfs-1.14.7=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -c -o bindfs.o bindfs.c
bindfs.c:1490:19: error: initialization of ‘void * (*)(struct fuse_conn_info
*)’ from incompatible pointer type ‘void * (*)(void)’
[-Wincompatible-pointer-types]
1490 | .init = bindfs_init,
| ^~~~~~~~~~~
bindfs.c:1490:19: note: (near initialization for ‘bindfs_oper.init’)
bindfs.c:621:14: note: ‘bindfs_init’ declared here
621 | static void *bindfs_init()
| ^~~~~~~~~~~
make[3]: *** [Makefile:445: bindfs.o] Error 1
make[3]: Leaving directory '/build/reproducible-path/bindfs-1.14.7/src'
make[2]: *** [Makefile:399: all-recursive] Error 1
make[2]: Leaving directory '/build/reproducible-path/bindfs-1.14.7'
make[1]: *** [Makefile:331: all] Error 2
make[1]: Leaving directory '/build/reproducible-path/bindfs-1.14.7'
dh_auto_build: error: make -j1 returned exit code 2
make: *** [debian/rules:5: binary] Error 255
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: bindfs
Source-Version: 1.18.4-0.1
Done: Bastian Germann <[email protected]>
We believe that the bug you reported is fixed in the latest version of
bindfs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bastian Germann <[email protected]> (supplier of updated bindfs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 29 Jan 2026 12:59:47 +0100
Source: bindfs
Architecture: source
Version: 1.18.4-0.1
Distribution: unstable
Urgency: medium
Maintainer: Eugene V. Lyubimkin <[email protected]>
Changed-By: Bastian Germann <[email protected]>
Closes: 1051054 1084458 1096368
Changes:
bindfs (1.18.4-0.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Import new upstream version. (Closes: #1051054, #1096368)
* Fix watch file by adding a trailing URL slash.
* Build with fuse3. (Closes: #1084458)
* Fix the install-sh license.
Checksums-Sha1:
ac96bef3d535c71f0f7df03967e51b96868e34ea 1576 bindfs_1.18.4-0.1.dsc
3a47f13021689cb75d230a9ef9777fdca156b946 432774 bindfs_1.18.4.orig.tar.gz
4165efa9552399aab3789521a1b429c42ddd510d 5320 bindfs_1.18.4-0.1.debian.tar.xz
c22fb651d2a6960d3ca71877a8ad65242bbd6675 5969
bindfs_1.18.4-0.1_source.buildinfo
Checksums-Sha256:
5c4df8574c6d66ea1b8870ae006ad5d0397ee4a123ec97f9ea5b8dc635f8ec1f 1576
bindfs_1.18.4-0.1.dsc
3266d0aab787a9328bbb0ed561a371e19f1ff077273e6684ca92a90fedb2fe24 432774
bindfs_1.18.4.orig.tar.gz
5758e7cd56b791d39ade5cb7309dac2c33091f03b7767073b5ef43350da76e5a 5320
bindfs_1.18.4-0.1.debian.tar.xz
99d08763944eb6e96a906a7cbad9151ead59d606841e30cdee7338734c97c2d6 5969
bindfs_1.18.4-0.1_source.buildinfo
Files:
941290a8c2be189ce31525fe11971ebd 1576 utils optional bindfs_1.18.4-0.1.dsc
000db2a598901783d35f7e0f1a1e2516 432774 utils optional
bindfs_1.18.4.orig.tar.gz
d09533b7377564a677bd00d21c7978bb 5320 utils optional
bindfs_1.18.4-0.1.debian.tar.xz
43f0b5c7f2a19de053a88f352e1e5898 5969 utils optional
bindfs_1.18.4-0.1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAml7ay8QHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFHAQC/0aUdO38SL8ywyji4m5JIs4OrVDb3aZuRmD
MjSrEjsVQ8ZtnP7GeFl0BGrWHT5z7ToNAnOuGajEAj8/dJy6ykmRgFp9y5eBuA8h
kGwdl5rou8Au6HznLSAsKpzDQCGyzSSrd+KoSSnxKxZXh6ursKLHsJzE9jUo1cMs
bAxLcMnOBIw0MkdCeflHtUosrWRFmqPMY1wuM6FrsrimFsAFw66FECc1ogiUsS2U
QNXwlnIlZM8lEco1ZNZ7HXxtVIIHT8Yzys1nWaAoHM6qxrdHH6sX0D7tds++Y+1S
sX1PJGdk6UKogU7aiYOHhojULjF/OV+ZzTaA4t/6WHpXT/wkNMtCn/RCktisR3sj
o4ELWp4ZEOqNIwVsBM1x6CKfB+UpIA2V31l6d7LXnuFKkCsfySfd6xUOyTbQxT+5
am6oJFbGjpTvkhY5TP9Hu3A5HrX8t21wzZ6hMpjqD9wYK8tc/wc5yPUIZ8mEXfqX
3fvRNX8jFyCSn3RYxOOvqotVLk3UQi0=
=8QOW
-----END PGP SIGNATURE-----
pgpWgLLi9DUjO.pgp
Description: PGP signature
--- End Message ---
