Skip to content
This repository was archived by the owner on Jan 9, 2026. It is now read-only.

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

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

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

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/10593536294 - 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
Contributor

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/meta.yaml) and found it was in an excellent condition.

@jakirkham

Copy link
Copy Markdown
Member

Looks like CI builds are failing with this error:

TEST START: /home/conda/feedstock_root/build_artifacts/linux-64/autoawq-0.1.6-py312haeebecf_2.conda
Traceback (most recent call last):
  File "/opt/conda/lib/python3.10/site-packages/conda_build/metadata.py", line 339, in select_lines
    if selector_cache[selector]:
KeyError: '"CXX"\\'

IIUC this is referring to the sed line in script where it looks like conda-build is now parsing the \[...\] as a selector even though it doesn't match that syntax

script: |
cat setup.py | sed 's/os.environ\["CC"\] = "g++"//' | sed 's/os.environ\["CXX"\] = "g++"//' > tmpsetup.py
mv tmpsetup.py setup.py
{{ PYTHON }} -m pip install . -vv --no-deps --no-build-isolation

In any event would normally suggest converting that sed line into a patch. That may still be useful just to clear this PR

However it appears this build is using autoawq version 0.1.6. Whereas the latest version appears to be 0.2.6

{% set name = "autoawq" %}
{% set version = "0.1.6" %}

Would add that the latest version no longer contains the os.environ compiler setting behavior that this was patching out

In short, perhaps simply updating to the latest version helps clean up this recipe and then this migration can be approached

@jakirkham

Copy link
Copy Markdown
Member

Actually this being addressed in PR: #13

Probably best to continue over there

@h-vetinari

Copy link
Copy Markdown
Member

Fixed in #13

@h-vetinari h-vetinari closed this Aug 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants