diff --git a/pkgs/os-specific/linux/sgx/sdk/ipp-crypto.nix b/pkgs/os-specific/linux/sgx/sdk/ipp-crypto.nix
index 78658736944b4..49ae08fb0df28 100644
--- a/pkgs/os-specific/linux/sgx/sdk/ipp-crypto.nix
+++ b/pkgs/os-specific/linux/sgx/sdk/ipp-crypto.nix
@@ -1,5 +1,5 @@
 {
-  gcc11Stdenv,
+  stdenv,
   fetchFromGitHub,
   cmake,
   nasm,
@@ -7,7 +7,7 @@
   python3,
   extraCmakeFlags ? [ ],
 }:
-gcc11Stdenv.mkDerivation rec {
+stdenv.mkDerivation rec {
   pname = "ipp-crypto";
   version = "2021.11.1";
 
@@ -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