Skip to content

Commit 10ca606

Browse files
authored
explain CUDA compiling isn't working
1 parent 98724a9 commit 10ca606

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

src/user/faq.rst

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,4 +71,10 @@ FAQ
7171
7272
x86_64-apple-darwin13.4.0-clang: No such file or directory
7373
74-
are a telltale sign that you are lacking compilers.
74+
are a telltale sign that you are lacking compilers.
75+
76+
:ref:`(Q) <faq_cuda_compiler_header>` **How can I compile CUDA (host or device) codes in my environment?**
77+
78+
Unfortunately, this is not possible with Conda-Forge's current infrastructure (``nvcc``, ``cudatoolkit``, etc) if there is no local CUDA Toolkit installation. In particular, the ``nvcc`` package provided on Conda-Forge is a *metapackage* wrapping an actual ``nvcc`` compiler for our CI to use; it does not contain the full ``nvcc`` compiler toolchain. One of the reasons is that CUDA headers like ``cuda.h``, ``cuda_runtime.h``, etc, are not redistributable according to NVIDIA's EULA, which are needed at compile time. Likewise, the ``cudatoolkit`` package only contains CUDA runtime libraries and not the compiler toolchain.
79+
80+
If you need to compile CUDA codes, even if they involve only CUDA host APIs, you will still need a valid CUDA Toolkit installed locally and use it.

0 commit comments

Comments
 (0)