Bug#1081124: ocaml-luv: FTBFS with gcc-14
Package: src:ocaml-luv
Version: 0.5.12-2
Severity: serious
Tags: ftbfs
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
--------------------------------------------------------------------------------
[...]
debian/rules binary
dh binary --with ocaml --buildsystem ocaml_dune
dh_update_autotools_config -O--buildsystem=ocaml_dune
cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead
dh_autoreconf -O--buildsystem=ocaml_dune
dh_ocamlinit -O--buildsystem=ocaml_dune
dh_auto_configure -O--buildsystem=ocaml_dune
dh_auto_build -O--buildsystem=ocaml_dune
dune build -j 2 -p luv,luv_unix
File "_build/.dune/default/src/c/dune", line 12, characters 9-30:
12 | (names c_generated_functions helpers)
^^^^^^^^^^^^^^^^^^^^^
(cd _build/default/src/c && /usr/bin/x86_64-linux-gnu-gcc -O2 -fno-strict-aliasing -fwrapv -pthread -fPIC -g -O2 -Werror=implicit-function-declaration -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -pthread -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -fno-strict-aliasing -fwrapv -pthread -fPIC -g -O2 -Werror=implicit-function-declaration -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -pthread -g -I /usr/lib/x86_64-linux-gnu/ocaml/5.2.0 -I /usr/lib/x86_64-linux-gnu/ocaml/5.2.0/bigarray-compat -I /usr/lib/x86_64-linux-gnu/ocaml/5.2.0/ctypes -I /usr/lib/x86_64-linux-gnu/ocaml/5.2.0/integers -I /usr/lib/x86_64-linux-gnu/ocaml/5.2.0/stdlib-shims -I /usr/lib/x86_64-linux-gnu/ocaml/5.2.0/threads -I /usr/lib/x86_64-linux-gnu/ocaml/5.2.0/unix -I . -o c_generated_functions.o -c c_generated_functions.c)
c_generated_functions.c: In function ‘luv_stub_155_luv_get_getnameinfo_trampoline’:
c_generated_functions.c:1155:4: error: initialization of ‘void (*)(uv_getnameinfo_t *, int, const char *, const char *)’ {aka ‘void (*)(struct uv_getnameinfo_s *, int, const char *, const char *)’} from incompatible pointer type ‘luv_getnameinfo_cb’ {aka ‘void (*)(struct uv_getnameinfo_s *, int, char *, char *)’} [-Wincompatible-pointer-types]
1155 | luv_get_getnameinfo_trampoline();
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
c_generated_functions.c: In function ‘luv_stub_156_luv_getnameinfo’:
c_generated_functions.c:1167:43: error: passing argument 3 of ‘luv_getnameinfo’ from incompatible pointer type [-Wincompatible-pointer-types]
1167 | int x931 = luv_getnameinfo(x924, x925, x926, x927, x928);
| ^~~~
| |
| void (*)(uv_getnameinfo_t *, int, const char *, const char *) {aka void (*)(struct uv_getnameinfo_s *, int, const char *, const char *)}
In file included from c_generated_functions.c:8:
helpers.h:177:64: note: expected ‘luv_getnameinfo_cb’ {aka ‘void (*)(struct uv_getnameinfo_s *, int, char *, char *)’} but argument is of type ‘void (*)(uv_getnameinfo_t *, int, const char *, const char *)’ {aka ‘void (*)(struct uv_getnameinfo_s *, int, const char *, const char *)’}
177 | uv_loop_t *loop, uv_getnameinfo_t *req, luv_getnameinfo_cb getnameinfo_cb,
| ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~
dh_auto_build: error: dune build -j 2 -p luv,luv_unix returned exit code 1
make: *** [debian/rules:9: binary] Error 25 shuffle=1513199080
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202409/
About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks.
Reply to: