On 8/18/21 7:56 PM, Sören Tempel wrote: > Hello, > > I just wanted to let you know that cryptsetup 2.4.0, contrary to 2.3.0, > no longer compiles with musl libc, e.g. as used on Alpine Linux, by > default. This is due to the fact that the external tokens code uses > dlvsym(3) which is a GNU extension not supported by musl. However, even > if support for external tokens is disabled (--disable-external-tokens) > `tests/all-symbols-test.c` fails to compile as it also requires dlvsym > and is not compiled conditionally. Hi, Please create an issue in upstream project https://gitlab.com/cryptsetup/cryptsetup/-/issues/new The dlvsym() is crucial to the LUKS2 external token extension, so perhaps the only solution would be to compile without external tokens for these constrained libc systems. And please, report this sooner - we released release-candidates exactly to find such problems. But people still do the same - waiting for final release, then complain that something is broken. We cannot fix things that we do not know about. If we can somehow automate build with non-glibc systems, I can add this to CI later. Thanks, Milan _______________________________________________ dm-crypt mailing list -- dm-crypt@xxxxxxxx To unsubscribe send an email to dm-crypt-leave@xxxxxxxx
