Skip to content

Rebuild for CUDA 12 w/arch + Windows support#9

Closed
regro-cf-autotick-bot wants to merge 3 commits into
conda-forge:mainfrom
regro-cf-autotick-bot:rebuild-cuda120-0-3_hcc64d6
Closed

Rebuild for CUDA 12 w/arch + Windows support#9
regro-cf-autotick-bot wants to merge 3 commits into
conda-forge:mainfrom
regro-cf-autotick-bot:rebuild-cuda120-0-3_hcc64d6

Conversation

@regro-cf-autotick-bot

Copy link
Copy Markdown
Contributor

This PR has been triggered in an effort to update cuda120.

Notes and instructions for merging this PR:

  1. Please merge the PR only after the tests have passed.
  2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.


Here are some more details about this specific migrator:

The transition to CUDA 12 SDK includes new packages for all CUDA libraries and build tools. Notably, the cudatoolkit package no longer exists, and packages should depend directly on the specific CUDA libraries (libcublas, libcusolver, etc) as needed. For an in-depth overview of the changes and to report problems see this issue. Please feel free to raise any issues encountered there. Thank you! 🙏


If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/6900435385, please use this URL for debugging.

The transition to CUDA 12 SDK includes new packages for all CUDA libraries and
build tools. Notably, the cudatoolkit package no longer exists, and packages
should depend directly on the specific CUDA libraries (libcublas, libcusolver,
etc) as needed. For an in-depth overview of the changes and to report problems
[see this issue]( conda-forge/conda-forge.github.io#1963 ).
Please feel free to raise any issues encountered there. Thank you! 🙏
@conda-forge-webservices

Copy link
Copy Markdown

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.

@jakirkham

Copy link
Copy Markdown
Member

@conda-forge-admin , please re-render

@jakirkham

Copy link
Copy Markdown
Member

When we looked at this in the past, we identified build errors related to issue: lightvector/KataGo#725

Hadrien even followed up in that issue seeking guidance. Unfortunately there hasn't been much progress

So it makes sense this is still stuck atm. Probably would entail patching to complete

@hadim

hadim commented Jan 22, 2025

Copy link
Copy Markdown
Member

Will test it again once #11 is merged

@hadim hadim closed this Jan 22, 2025
@h-vetinari

Copy link
Copy Markdown
Member

You can't really avoid picking up the equivalent of this migration, because any rerender will get those changes (well, unless you explicitly skip cuda 12)

@hadim

hadim commented Jan 22, 2025

Copy link
Copy Markdown
Member

You can't really avoid picking up the equivalent of this migration, because any rerender will get those changes (well, unless you explicitly skip cuda 12)

Note that cuda 12 is working on linux-64 and linux-aarch64

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 this pull request may close these issues.

4 participants