From e28c5cd7ac73026057b1dc2783c081340dc04358 Mon Sep 17 00:00:00 2001 From: Alyssa Ross Date: Mon, 24 Jan 2022 13:01:46 +0000 Subject: [PATCH] pkgsStatic.cryptsetup: don't --enable-static-cryptsetup MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --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. --- pkgs/os-specific/linux/cryptsetup/default.nix | 2 -- 1 file changed, 2 deletions(-) diff --git a/pkgs/os-specific/linux/cryptsetup/default.nix b/pkgs/os-specific/linux/cryptsetup/default.nix index 27f32c648131..a9bd508d16ec 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 ];