Add CUDA 11.1 migrator - Githubissues

conda-forge / nvcc-feedstock

A conda-smithy repository for nvcc.

BSD 3-Clause "New" or "Revised" License

12 stars 23 forks source link

Add CUDA 11.1 migrator #50

Closed jaimergp closed 3 years ago

jaimergp commented 3 years ago

Checklist

[X] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Blocked by https://github.com/conda-forge/conda-forge-ci-setup-feedstock/pull/131 and https://github.com/conda-forge/docker-images/pull/160

conda-forge-linter commented 3 years ago

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

conda-forge-linter commented 3 years ago

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

Failed to even lint the recipe, probably because of a conda-smithy bug :cry:. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

conda-forge-linter commented 3 years ago

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

jaimergp commented 3 years ago

That doesn't work even if tests are successful. CUDA 11 is back to 2.12 sysroots.

jaimergp commented 3 years ago

Ok, using cdt_name does work. I guess that's more sustainable in the future (and makes more sense since 2.17 is tied to cos7?). If this is not ok, we need to figure out a clean way to state that CUDA 11.0+ requires glibc 2.17+...

jaimergp commented 3 years ago

I'll probably get back to this soon. Looks like all the missing pieces are available now!