pkgsStatic.cryptsetup: don't --enable-static-cryptsetup

--enable-static-cryptsetup adds binaries suffixed with .static,
e.g. cryptsetup.static, and those binaries have extra flags set to
enable them to be built statically.  It doesn't change how the main
binaries are built — they're compiled correctly because pkgsStatic
sets up all the necessary compiler flag anyway.  So as far as I can
tell, all --enable-static-cryptsetup gets us is duplicate binaries
that take up disk space unnecessarily.

1 files changed, 0 insertions, 2 deletions

diff --git a/pkgs/os-specific/linux/cryptsetup/default.nix b/pkgs/os-specific/linux/cryptsetup/default.nix
index 27f32c64813..a9bd508d16e 100644
--- a/pkgs/os-specific/linux/cryptsetup/default.nix
+++ b/pkgs/os-specific/linux/cryptsetup/default.nix
@@ -31,8 +31,6 @@ stdenv.mkDerivation rec {
     "--enable-cryptsetup-reencrypt"
     "--with-crypto_backend=openssl"
     "--disable-ssh-token"
-  ] ++ lib.optionals stdenv.hostPlatform.isStatic [
-    "--enable-static-cryptsetup"
   ];
 
   nativeBuildInputs = [ pkg-config ];