optee-builder: use stdenv as opposed to gccStdenv

should be the same in our use case, but stdenv is more standard.
This commit is contained in:
Jörg Thalheim
2025-11-04 12:34:11 +01:00
parent e598a4ca2f
commit f2e49f279c
2 changed files with 6 additions and 6 deletions

View File

@@ -4,9 +4,9 @@
}:
let
inherit (pkgs.buildPackages) python3;
toolchain = pkgs.gccStdenv.cc;
binutils = pkgs.gccStdenv.cc.bintools.bintools_bin;
cpp = pkgs.gccStdenv.cc;
toolchain = pkgs.stdenv.cc;
binutils = pkgs.stdenv.cc.bintools.bintools_bin;
cpp = pkgs.stdenv.cc;
in
pkgs.stdenv.mkDerivation {
pname = "imx95-optee-os";

View File

@@ -13,9 +13,9 @@
}:
let
inherit (pkgs.buildPackages) python3;
toolchain = pkgs.gccStdenv.cc;
binutils = pkgs.gccStdenv.cc.bintools.bintools_bin;
cpp = pkgs.gccStdenv.gcc;
toolchain = pkgs.stdenv.cc;
binutils = pkgs.stdenv.cc.bintools.bintools_bin;
cpp = pkgs.stdenv.gcc;
# Determine PLATFORM and PLATFORM_FLAVOR from platformFlavor
# Format can be either "imx-mx93evk" (full platform string) or "mx8mpevk" (just flavor, platform is "imx")