Loading pkgs/os-specific/linux/sgx/sdk/ipp-crypto.nix +8 −2 Original line number Diff line number Diff line { gcc11Stdenv, stdenv, fetchFromGitHub, cmake, nasm, Loading @@ -7,7 +7,7 @@ python3, extraCmakeFlags ? [ ], }: gcc11Stdenv.mkDerivation rec { stdenv.mkDerivation rec { pname = "ipp-crypto"; version = "2021.11.1"; Loading @@ -25,6 +25,12 @@ gcc11Stdenv.mkDerivation rec { ] ++ extraCmakeFlags; # Yes, it seems bad for a cryptography library to trigger this # warning. We previously pinned an EOL GCC which avoided it, but this # issue is present regardless of whether we use a compiler that flags # it up or not; upstream just doesn’t test with modern compilers. env.NIX_CFLAGS_COMPILE = "-Wno-error=stringop-overflow"; nativeBuildInputs = [ cmake nasm Loading Loading
pkgs/os-specific/linux/sgx/sdk/ipp-crypto.nix +8 −2 Original line number Diff line number Diff line { gcc11Stdenv, stdenv, fetchFromGitHub, cmake, nasm, Loading @@ -7,7 +7,7 @@ python3, extraCmakeFlags ? [ ], }: gcc11Stdenv.mkDerivation rec { stdenv.mkDerivation rec { pname = "ipp-crypto"; version = "2021.11.1"; Loading @@ -25,6 +25,12 @@ gcc11Stdenv.mkDerivation rec { ] ++ extraCmakeFlags; # Yes, it seems bad for a cryptography library to trigger this # warning. We previously pinned an EOL GCC which avoided it, but this # issue is present regardless of whether we use a compiler that flags # it up or not; upstream just doesn’t test with modern compilers. env.NIX_CFLAGS_COMPILE = "-Wno-error=stringop-overflow"; nativeBuildInputs = [ cmake nasm Loading