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

Bump GCC pins for CUDA 12.6 #6736

Closed
h-vetinari opened this issue Nov 24, 2024 · 3 comments · Fixed by #6849
Closed

Bump GCC pins for CUDA 12.6 #6736

h-vetinari opened this issue Nov 24, 2024 · 3 comments · Fixed by #6849

Comments

@h-vetinari
Copy link
Member

As a follow-up to #6720 - I just realised that bumping to 12.6 means we should have updated GCC pins as well. The upstream docs (found the reference in conda-forge/nvcc-feedstock#51) say that nvcc compatible with "GCC 6.x - 13.2". We're on 13.3 though.

Is the minor-level bound really enforced? I don't remember that in previous nvcc constraints for gcc (which were major-only AFAIR).

Originally posted by @h-vetinari in #6720 (comment)

@h-vetinari
Copy link
Member Author

@bdice
Copy link
Contributor

bdice commented Nov 27, 2024

I've looked at this before. I'm pretty sure that matching the minor version is not enforced, but major version support is enforced. In other words, gcc 13.3 should be fine if nvcc claims support for 13.2, but gcc 14.0 would not work.

@h-vetinari
Copy link
Member Author

I tried this by overriding the pinning in a feedstock (h-vetinari/faiss-split-feedstock@a4002e0). It works on CUDA 12.6, but doesn't on CUDA 12.4 for ppc, where it yields:

Could not solve for environment specs
The following packages are incompatible
├─ cuda-nvcc_linux-ppc64le =12.4 * is installable with the potential options
│  ├─ cuda-nvcc_linux-ppc64le 12.4.131 would require
│  │  └─ cuda-nvcc-tools =12.4.131 *, which requires
│  │     └─ gcc_impl_linux-64 >=6,<13 *, which can be installed;
│  └─ [...]
└─ gxx_linux-ppc64le =13 * is not installable because there are no viable options

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