Describe the bug

The context, copied pretty much as is from matrix: cudaPackages.cuda_nvcc builds cuda programs, and behind the scenes it uses gcc for that. This is controlled by the CMAKE_CUDA_HOST_COMPILER variable.

If we just set CMAKE_CUDA_HOST_COMPILER to cudaPackages.cudatoolkit.cc (which currently equals wrapCCWith { cc = gcc11Stdenv.cc.cc; libcxx = gcc12Stdenv.cc.cc.lib; }), the build ends up still linking gcc11's libstdc++, which is explicitly not what we're trying to do, and results in broken builds

If we make a customStdenv = overrideCC stdenv (wrapCCWith ( ... }) (currently, cudaPackages.backendStdenv, to be renamed into cudaStdenv) and use its mkDerivation to build the cuda program, it correctly links gcc12's libstdc++.

This is unexpected, because the actual host compiler (e.g. used for .cc and .cpp files) in the derivation is still gcc12. Gcc11 is only visible to the build through the aforementioned CMAKE_CUDA_HOST_COMPILER and it is wrapped anyway

Steps To Reproduce

• Unsuccessful usage of wrapCCWith ...
  • Logs: https://github.com/SomeoneSerge/nix-findcudatoolkit-cmake/actions/runs/4652383894/jobs/8232564012 (the error means that we've linked gcc11's libstdc++, you can verify this by removing cppzmq from target_link_libraries and observing the output of ldd in the logs)
  • Expression: https://github.com/SomeoneSerge/nix-findcudatoolkit-cmake/blob/3eebed75174fb4e81c9d59a447ed6c4843cc83bf/use-cudatoolkit-root.nix (called with default arguments, i.e. stdenv = pkgs.stdenv)
• Successful usage of overrideCC (wrapCCWith ...)
  • https://github.com/SomeoneSerge/nix-findcudatoolkit-cmake/actions/runs/4652383894/jobs/8232564130
  • Expression: https://github.com/SomeoneSerge/nix-findcudatoolkit-cmake/blob/3eebed75174fb4e81c9d59a447ed6c4843cc83bf/use-cudatoolkit-root.nix (same, but called with stdenv = overrideCC (wrapCCWith ...))

Another version of the same example: https://gist.github.com/SomeoneSerge/cc47a75885f8b9ea267456675e115cfe#file-vanilla-log-L59

Expected behavior

Both builds link gcc12's libstdc++ and succeed

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

wrapCCWith practically just adds the chosen libstdc++ into propagatedBuildInput, and we maybe abuse the function

Notify maintainers

@NixOS/cuda-maintainers