-
-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
document CUDA builds #1226
document CUDA builds #1226
Conversation
@jakirkham @kkraus14 can you double-check the CUDA info in this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jaimergp I'm approving mostly the text and readability b/c I'm not too familiar with the process used here.
@jakirkham or @kkraus14 can you take a look and merge?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, one suggestion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thanks Jaime! 😄
Made a few minor suggestions above. Also generally agree with the points others have made here.
Just noting that this is not ready to merge yet, since some of the workarounds here described wouldn't apply after conda-forge/nvcc-feedstock#58 is approved and merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks again for the work here Jaime! 😄
Included a couple minor suggestions below.
Co-authored-by: jakirkham <jakirkham@gmail.com>
build: | ||
... | ||
missing_dso_whitelist: | ||
- "*/nvcuda.dll" # [win] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any way to add this the global conda-forge settings?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not that I know of.
Would be good if people can take another look 🙂 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sometime in the future it would be good to document what we now think about gcc versions and cuda versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work here and elsewhere in the CF territory, @jaimergp! LGTM. I left a question for everyone here, but it need not be addressed in this PR.
* ``nvcc``: Nvidia's EULA does not allow the redistribution of compilers and drivers. Instead, we | ||
provide a wrapper package that locates the CUDA installation in the system. The main role of this | ||
package is to set some environment variables (``CUDA_HOME``, ``CUDA_PATH``, ``CFLAGS`` and others), | ||
as well as wrapping the real ``nvcc`` executable to set some extra command line arguments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand this PR is for recipe maintainers, but I am wondering if we could mention this somewhere that the nvcc
package is not for end users to install and use (as it's just a wrapper over the real compiler, which is missing)? I've seen several bug reports (including my own) in which the users do not have a local CUDA Toolkit installation and mistakenly think installing nvcc
would enable them to compile.
@beckermr What specifically do you have in mind? |
Likely the interactions/restrictions being discussed in conda-forge/nvcc-feedstock#51, conda-forge/conda-forge-pinning-feedstock#1000, etc...? |
Yup @h-vetinari has the right idea. There has been back and forth on this. As more people start to use CUDA builds, there will be more questions etc. |
I see. Indeed it makes sense. Thanks @h-vetinari @beckermr. We should probably address it (including conda-forge/conda-forge-pinning-feedstock#1053) before the CUDA 11.1 migration starts. |
Will close #901