about summary refs log tree commit diff
path: root/nixpkgs/pkgs/development/cuda-modules/backend-stdenv.nix
blob: 10fedd1e6f271c917f8152d6d59301368d316eba (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
{
  lib,
  nvccCompatibilities,
  cudaVersion,
  buildPackages,
  overrideCC,
  stdenv,
  wrapCCWith,
}:
let
  gccMajorVersion = nvccCompatibilities.${cudaVersion}.gccMaxMajorVersion;
  # We use buildPackages (= pkgsBuildHost) because we look for a gcc that
  # runs on our build platform, and that produces executables for the host
  # platform (= platform on which we deploy and run the downstream packages).
  # The target platform of buildPackages.gcc is our host platform, so its
  # .lib output should be the libstdc++ we want to be writing in the runpaths
  # Cf. https://github.com/NixOS/nixpkgs/pull/225661#discussion_r1164564576
  nixpkgsCompatibleLibstdcxx = buildPackages.gcc.cc.lib;
  nvccCompatibleCC = buildPackages."gcc${gccMajorVersion}".cc;

  cc = wrapCCWith {
    cc = nvccCompatibleCC;

    # This option is for clang's libcxx, but we (ab)use it for gcc's libstdc++.
    # Note that libstdc++ maintains forward-compatibility: if we load a newer
    # libstdc++ into the process, we can still use libraries built against an
    # older libstdc++. This, in practice, means that we should use libstdc++ from
    # the same stdenv that the rest of nixpkgs uses.
    # We currently do not try to support anything other than gcc and linux.
    libcxx = nixpkgsCompatibleLibstdcxx;
  };
  cudaStdenv = overrideCC stdenv cc;
  passthruExtra = {
    inherit nixpkgsCompatibleLibstdcxx;
    # cc already exposed
  };
  assertCondition = true;
in
lib.extendDerivation assertCondition passthruExtra cudaStdenv