-
-
Notifications
You must be signed in to change notification settings - Fork 487
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
cxx_compiler_version incompatible with nvcc #1000
Comments
From conda-forge/faiss-split-feedstock#18 (comment) :
Smells like conda/conda-build#3974 ... |
Also likely related to issue ( conda-forge/nvcc-feedstock#51 ). |
@isuruf Does it make sense to change this part of the migrator conda-forge-pinning-feedstock/recipe/migrations/cuda110.yaml Lines 29 to 34 in 76faade
as follows?
This way when using CUDA 11.0 we can use gcc 9, which is recommend in the Installation Guide, but for older CUDA we use gcc 7. |
No, only selectors allowed are the os/arch selectors. |
I see. So is there a way to enable gcc 9 for CUDA 11+? |
btw for context: with #1052 all CUDA builds fall back to gcc 7 now, so it works for all CUDA versions (9.2 - 11.0). The discussion is about enabling gcc 9 for CUDA 11.0+ only. |
I can't speak about the migrator, and how it's affected by updates to zip-keys in the pinning, but generally, it should be possible to add |
Closing this out as out-of-date (was solved in the meantime by conda-forge/conda-smithy#1544 and follow-ups). |
On the faiss-feedstock, we're building per cuda-version, and with the recent compiler upgrades, this now hits the limit for what nvcc supports:
I've been trying what feels like dozens of different ways (e.g. here) to work around this using a local
conda_build_config.yaml
, but it seems the pinning always overrides my values in_combine_spec_dictionaries
and then I get zipkey-length-conflicts.Rather than trying to figure out how to fix this on a per-feedstock basis, I'm I'm now thinking that this should be fixed on the cfp-side directly (hence this issue), because presumably other recipes will also (eventually) be affected.
The text was updated successfully, but these errors were encountered: