Bug#963933: glib2.0: autopkgtext: ld: cannot find -lcryptsetup
Simon McVittie
smcv at debian.org
Mon Jun 29 00:16:49 BST 2020
On Sun, 28 Jun 2020 at 22:00:58 +0200, Chris Hofstaedtler wrote:
> the autopkgtest suite offers quite interesting behaviour:
> With an installed libcryptsetup-dev, ld fails with "cannot find
> -lcryptsetup".
...
> I imagine this might be caused by libcryptsetup-dev not shipping an
> .a library.
This means that GLib could previously be successfully statically linked
(and we had a test to prove it), and now it cannot.
Do you consider this to be a deliberate change? Is statically linking
a library that depends on libmount no longer supported?
(If it is, then we might as well stop providing static libraries for
GLib too, and you might as well stop providing static libraries for
libmount.)
smcv
More information about the pkg-gnome-maintainers
mailing list