-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Headers are only in $PREFIX/targets
folder but aren't in $PREFIX/include
#11
Comments
Copying response from: conda-forge/staged-recipes#22127 (comment)
If there is a use case for other compilers to be used here we can add the symlinks to |
FWIW even with the pre-CUDA 12 CF infra today these headers do not exist in |
With conda-forge/cupy-feedstock#199, I was wrong. It seems to be a blocking bug to certain packages that knew to look for headers in |
Given there is still work needed for |
I would think the fix for cuda-nvcc is likely independent. We either need a way to tell the host compiler (outside of nvcc) where the headers are, or patch the build system, or make a symlink so that the headers can be find in |
FWIW am using that issue as sort of a catch all for remaining compiler work Anyways agree with following up tomorrow. We already got a lot of hard work done! 😀 |
I have also run into this issue with conda-forge/libmagma-feedstock#4. |
We add these headers to host compiler's include path ( Would be interested to know what is happening when they are not getting picked up |
Is that path added for the host compilers if someone isn't using nvcc at all? I.E. it's 100% valid to have a |
Currently there's not an easy way to use the CUDA packages without also having the CUDA compiler installed. This would be a reasonable issue to file on the |
EDIT: Missed this line: https://github.com/conda-forge/cuda-nvcc-feedstock/blob/deab0342455db4462ef55f487a7b8dd865760e6a/recipe/activate.sh#L26 We may want to consider moving some kind of logic like this into the individual package feedstocks so that it can influence the host compilers even if the |
Only suggestion is to raise a |
This isn't a Any reason we can't use this issue to continue discussing? |
Because Currently the flags are in Perhaps another place an issue could be is in the compiler stack somewhere. As exactly where this issue would go was unclear, thought |
Solution to issue cannot be found in the documentation.
Issue
In the
libcublas-dev
package I was expecting the headers to either be added or symlinked in the$PREFIX/include
folder, but they're only in the$PREFIX/targets
folder. Compilers won't search here by default as far as I know so this should probably be corrected.Installed packages
Environment info
The text was updated successfully, but these errors were encountered: