gentoo.LinuxHowtos.org
Details of dev-util/nvidia-cuda-toolkit:
Description: NVIDIA CUDA Toolkit (compiler and friends)Homepage: https://developer.nvidia.com/cuda-zone
available versions:
releases | alpha | amd64 | arm | hppa | ia64 | mips | ppc | ppc64 | ppc macos | s390 | sh | sparc | x86 | USE-Flags | dependencies | ebuild warnings |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
nvidia-cuda-toolkit-12.6.1 | - | ~ | - | - | - | - | - | - | - | - | - | - | - | debugger examples nsight profiler rdma vis-profiler sanitizer | show | gcc > ${b} will not work with CUDA Make sure you set an earlier version of gcc with gcc-config or append --compiler-bindir= pointing to a gcc bindir like --compiler-bindir=${EPREFIX}/usr/*pc-linux-gnu/gcc-bin/gcc${b} to the nvcc compiler flags nvidia-drivers restrict access to performance counters. |
nvidia-cuda-toolkit-12.6.0 | - | ~ | - | - | - | - | - | - | - | - | - | - | - | debugger examples nsight profiler rdma vis-profiler sanitizer | show | gcc > ${b} will not work with CUDA Make sure you set an earlier version of gcc with gcc-config or append --compiler-bindir= pointing to a gcc bindir like --compiler-bindir=${EPREFIX}/usr/*pc-linux-gnu/gcc-bin/gcc${b} to the nvcc compiler flags nvidia-drivers restrict access to performance counters. |
nvidia-cuda-toolkit-12.5.1 | - | ~ | - | - | - | - | - | - | - | - | - | - | - | debugger examples nsight profiler rdma vis-profiler sanitizer | show | gcc > ${b} will not work with CUDA Make sure you set an earlier version of gcc with gcc-config or append --compiler-bindir= pointing to a gcc bindir like --compiler-bindir=${EPREFIX}/usr/*pc-linux-gnu/gcc-bin/gcc${b} to the nvcc compiler flags nvidia-drivers restrict access to performance counters. |
nvidia-cuda-toolkit-12.5.0-r1 | - | ~ | - | - | - | - | - | - | - | - | - | - | - | debugger examples nsight profiler rdma vis-profiler sanitizer | show | gcc > ${b} will not work with CUDA Make sure you set an earlier version of gcc with gcc-config or append --compiler-bindir= pointing to a gcc bindir like --compiler-bindir=${EPREFIX}/usr/*pc-linux-gnu/gcc-bin/gcc${b} to the nvcc compiler flags nvidia-drivers restrict access to performance counters. |
nvidia-cuda-toolkit-12.4.1 | - | ~ | - | - | - | - | - | - | - | - | - | - | - | debugger examples nsight profiler rdma vis-profiler sanitizer | show | gcc > ${b} will not work with CUDA Make sure you set an earlier version of gcc with gcc-config or append --compiler-bindir= pointing to a gcc bindir like --compiler-bindir=${EPREFIX}/usr/*pc-linux-gnu/gcc-bin/gcc${b} to the nvcc compiler flags nvidia-drivers restrict access to performance counters. |
nvidia-cuda-toolkit-12.4.0 | - | ~ | - | - | - | - | - | - | - | - | - | - | - | debugger examples nsight profiler rdma vis-profiler sanitizer | show | gcc > ${b} will not work with CUDA Make sure you set an earlier version of gcc with gcc-config or append --compiler-bindir= pointing to a gcc bindir like --compiler-bindir=${EPREFIX}/usr/*pc-linux-gnu/gcc-bin/gcc${b} to the nvcc compiler flags nvidia-drivers restrict access to performance counters. |
nvidia-cuda-toolkit-12.3.2 | - | ~ | - | - | - | - | - | - | - | - | - | - | - | debugger examples nsight profiler rdma vis-profiler sanitizer | show | gcc > ${b} will not work with CUDA Make sure you set an earlier version of gcc with gcc-config or append --compiler-bindir= pointing to a gcc bindir like --compiler-bindir=${EPREFIX}/usr/*pc-linux-gnu/gcc-bin/gcc${b} to the nvcc compiler flags nvidia-drivers restrict access to performance counters. |
nvidia-cuda-toolkit-11.8.0-r4 | - | ~ | - | - | - | - | - | - | - | - | - | - | - | debugger nsight profiler vis-profiler sanitizer | show | gcc > ${b} will not work with CUDA Make sure you set an earlier version of gcc with gcc-config or append --compiler-bindir= pointing to a gcc bindir like --compiler-bindir=${EPREFIX}/usr/*pc-linux-gnu/gcc-bin/gcc${b} to the nvcc compiler flags nvidia-drivers restrict access to performance counters. |
+ stable
~ testing
- not available
some ebuild warning depend on specific use-flags or architectures, all ebuild-warnings are shown.