Source: glib2.0 Severity: serious Version: 2.64.3-1 Dear glib2.0 Maintainers,
the autopkgtest suite offers quite interesting behaviour: With an installed libcryptsetup-dev, ld fails with "cannot find -lcryptsetup". Log: https://ci.debian.net/data/autopkgtest/testing/amd64/g/glib2.0/6071882/log.gz autopkgtest [00:19:30]: test build: preparing testbed .. Selecting previously unselected package libcryptsetup-dev:amd64. Preparing to unpack .../19-libcryptsetup-dev_2%3a2.3.3-1_amd64.deb ... Unpacking libcryptsetup-dev:amd64 (2:2.3.3-1) ... .. autopkgtest [00:19:45]: test build: -----------------------] autopkgtest [00:19:45]: test build: - - - - - - - - - - results - - - - - - - - - - build PASS (superficial) autopkgtest [00:19:45]: test build-static: preparing testbed .. + gcc -static -o gio-static gio.c -pthread -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -lgio-2.0 -ldl -pthread -lresolv -lgmodule-2.0 -pthread -ldl -lz -lmount -lblkid -lcryptsetup -lselinux -lsepol -lpcre2-8 -pthread -lgobject-2.0 -pthread -lffi -lglib-2.0 -pthread -lpcre -pthread /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libgmodule-2.0.a(gmodule.c.o): in function `g_module_open': (.text+0x703): warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/bin/ld: cannot find -lcryptsetup I imagine this might be caused by libcryptsetup-dev not shipping an .a library. This prevents libmount1/util-linux to transition. Please investigate and hopefully fix the problem at hand. Thanks, Chris
