-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
PowerPC builds #21
Comments
Yep, I think you have more-or-less outlined the issues that have been in our heads. Thanks for doing that. 🙂 We've requested CentOS 6 ppc64le images in this upstream issue. This may happen as part of making multiarch Docker images tracked in this upstream issue. That said, our ppc64le stack uses CentOS 7 anyways. This due to the fact that there are only CentOS 7 ppc64le base images. So using CentOS 7 for ppc64le GPU builds would be fine and is already compatible with how we build things on that architecture. We did start working on CentOS 7-based NVIDIA-derived ppc64le images in PR ( conda-forge/docker-images#113 ). However this ran into issues due to the lack of more recent |
Why can't we distribute the cudatoolkit? Debian ships the libraries and the compiler. (Maybe with NVIDIA permission?) |
We're investigating this internally to see if there's any licensing / legal issues and will report back. |
Thanks for the detailed update, @jakirkham! I'll keep an eye on this. |
There was no ppc64le version of CENTOS6. It predates ppc64le being an official Linux arch so we'd have to start with CENTOS7 for ppc64le. I agree, it would be great if forge could distribute the cuda toolkit! |
@kkraus14 Any update for this inquiry? Thanks! |
It would be nice to add support for
ppc64le
architectures. I don't know if the current system would work OK for this situation, since it assumes one CUDA version = one Docker image.Even if that gets solved, there are some external barriers:
conda-forge
would eventually migrate to CentOS 7, but I have no idea when that's going to happen.cudatoolkit
forppc64le
, but only forv9.0
.I'll leave this here for future reference and update as needed. Thanks!
The text was updated successfully, but these errors were encountered: