-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
libdevice not found when using jax with nvidia drivers installed #283
Comments
@conda-forge/core @jakirkham Do you all have any ideas here? |
So Originally In CUDA 12.2, If these are hard dependencies, the recipe here could be updated to include these. In the interim, users could consider installing one of these packages themselves based on their needs Hope that helps. Please feel free to ask more questions 🙂 |
cc @conda-forge/cuda (for vis) |
|
Ah thanks for pointing that out. See that above Also noticing the path the package uses appears comes from the recipes Looks like the relevant bits are in |
Yeah think this just needs Also think this should be jaxlib-feedstock/recipe/meta.yaml Line 85 in a10f0e8
As a side note, think we can drop this workaround as well. It was fixed upstream: conda-forge/cuda-cupti-feedstock#14 jaxlib-feedstock/recipe/meta.yaml Lines 86 to 87 in a10f0e8
|
I'm including these fixes now in #281 (comment) |
As conda-forge recently moved to CUDA 12.6 ( conda-forge/conda-forge-pinning-feedstock#6720 ), think we can change xref: #283 (comment) |
If I am not wrong jax cuda support depends at runtime on ptxas, so I guess we need to keep cuda-nvcc-tools, but if libdevice is contained in cuda-nvvm-tools we need to add also that as a dependency. |
Ah ok. Yeah would stick with
|
Solution to issue cannot be found in the documentation.
Issue
With this test program and
/dev/nvidia*
being present in the systemfails with
jax fails to find
libdevice
Testing with
strace
The default search paths seem wrong. conda installs
libdevice
for example inlib/nvvm/libdevice
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: