Skip to content
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

jax-releases dependencies only for cuda* for linux #328

Open
GraoMelo opened this issue May 2, 2024 · 0 comments · May be fixed by #329
Open

jax-releases dependencies only for cuda* for linux #328

GraoMelo opened this issue May 2, 2024 · 0 comments · May be fixed by #329

Comments

@GraoMelo
Copy link

GraoMelo commented May 2, 2024

Hello, congratulations on the initiative to share the project on GitHub.
I would like to suggest that the hardware requirements be explicitly stated in the documentation.

When analyzing the dependencies:

jax[cuda12-pip]==0.4.25 -f https://storage.googleapis.com/jax-releases/jax_cuda_releases.html

In my view, it makes sense, but on the URL:

https://storage.googleapis.com/jax-releases/jax_cuda_releases.html

there are many files:

cuda100/jaxlib-0.1.52+cuda100-cp36-none-manylinux2010_x86_64.whl
cuda101/jaxlib-0.1.52+cuda101-cp36-none-manylinux2010_x86_64.whl
cuda102/jaxlib-0.1.52+cuda102-cp36-none-manylinux2010_x86_64.whl
cuda11/jaxlib-0.1.73+cuda11.cudnn805-cp37-none-manylinux2010_x86_64.whl

or even:

cuda110/jaxlib-0.1.52+cuda110-cp36-none-manylinux2010_x86_64.whl
cuda111/jaxlib-0.1.56+cuda111-cp36-none-manylinux2010_x86_64.whl

or still

cuda112/jaxlib-0.1.65+cuda112-cp39-none-manylinux2010_x86_64.whl

cuda12/jaxlib-0.4.10+cuda12.cudnn88-cp310-cp310-manylinux2014_x86_64.whl

All the files have the suffix:

manylinux20yy = yy year year
_x86_64.whl = X86 or amd64 architecture

In other words, little compatibility with Unix or Windows.
I'm not saying it's not possible to emulate via WSL or even containers or virtual machines, but it's not written anywhere that the support is only for Linux when using the CUDA modules.

GraoMelo added a commit to GraoMelo/grok-1 that referenced this issue May 2, 2024
@GraoMelo GraoMelo linked a pull request May 2, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
@GraoMelo and others