talexander/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Releases Activity

sgx-sdk: unpin GCC

Browse Source
This commit is contained in:
Emily 2025-08-08 18:22:54 +01:00
parent 3cca2c60f7
commit 0ef1fe5c04
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
pkgs/os-specific/linux/sgx/sdk/ipp-crypto.nix
View File

@ -1,5 +1,5 @@
{ {
gcc11Stdenv, stdenv,
fetchFromGitHub, fetchFromGitHub,
cmake, cmake,
nasm, nasm,
@ -7,7 +7,7 @@
python3, python3,
extraCmakeFlags ? [ ], extraCmakeFlags ? [ ],
}: }:
gcc11Stdenv.mkDerivation rec { stdenv.mkDerivation rec {
pname = "ipp-crypto"; pname = "ipp-crypto";
version = "2021.11.1"; version = "2021.11.1";
@ -25,6 +25,12 @@ gcc11Stdenv.mkDerivation rec {
] ]
++ extraCmakeFlags; ++ 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 = [ nativeBuildInputs = [
cmake cmake
nasm nasm