Skip to content

Upgrade to CUDA 12.9 + linux_aarch64#1

Merged
weiji14 merged 8 commits into
conda-forge:mainfrom
regro-cf-autotick-bot:rebuild-cuda129-0-1_hcfdc9e
Sep 19, 2025
Merged

Upgrade to CUDA 12.9 + linux_aarch64#1
weiji14 merged 8 commits into
conda-forge:mainfrom
regro-cf-autotick-bot:rebuild-cuda129-0-1_hcfdc9e

Conversation

@regro-cf-autotick-bot
Copy link
Copy Markdown
Contributor

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

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:

CUDA 12.8 added support for architectures sm_100, sm_101 and sm_120,
while CUDA 12.9 further added sm_103 and sm_121. To build for these,
maintainers will need to modify their existing list of specified architectures
(e.g. CMAKE_CUDA_ARCHITECTURES, TORCH_CUDA_ARCH_LIST, etc.)
for their package. A good balance between broad support and storage
footprint (resp. compilation time) is to add sm_100 and sm_120.

Since CUDA 12.8, the conda-forge nvcc package now sets CUDAARCHS and
TORCH_CUDA_ARCH_LIST in its activation script to a string containing all
of the supported real architectures plus the virtual architecture of the
latest. Recipes for packages who use these variables to control their build
but do not want to build for all supported architectures will need to override
these variables in their build script.

ref: https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html#new-features


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/17384134486 - please use this URL for debugging.

@conda-forge-admin
Copy link
Copy Markdown
Contributor

conda-forge-admin commented Sep 1, 2025

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

CUDA 12.8 added support for architectures `sm_100`, `sm_101` and `sm_120`,
while CUDA 12.9 further added `sm_103` and `sm_121`. To build for these,
maintainers will need to modify their existing list of specified architectures
(e.g. `CMAKE_CUDA_ARCHITECTURES`, `TORCH_CUDA_ARCH_LIST`, etc.)
for their package. A good balance between broad support and storage
footprint (resp. compilation time) is to add `sm_100` and `sm_120`.

Since CUDA 12.8, the conda-forge nvcc package now sets `CUDAARCHS` and
`TORCH_CUDA_ARCH_LIST` in its activation script to a string containing all
of the supported real architectures plus the virtual architecture of the
latest. Recipes for packages who use these variables to control their build
but do not want to build for all supported architectures will need to override
these variables in their build script.

ref: https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html#new-features
…5.09.18.12.55.27

Other tools:
- conda-build 25.7.0
- rattler-build 0.47.0
- rattler-build-conda-compat 1.4.6
@weiji14 weiji14 force-pushed the rebuild-cuda129-0-1_hcfdc9e branch from 62ee354 to 17625d9 Compare September 18, 2025 21:06
@weiji14 weiji14 self-requested a review as a code owner September 18, 2025 21:06
@weiji14
Copy link
Copy Markdown
Member

weiji14 commented Sep 18, 2025

@conda-forge-admin please rerender

@weiji14 weiji14 changed the title Upgrade to CUDA 12.9 Upgrade to CUDA 12.9 + linux_aarch64 Sep 18, 2025
@weiji14 weiji14 marked this pull request as draft September 19, 2025 01:58
@weiji14
Copy link
Copy Markdown
Member

weiji14 commented Sep 19, 2025

Getting this error on the linux_aarch64_cuda_compiler_version12.9python3.13.____cp313 build at https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=1344215&view=logs&j=010ccbe2-65a2-511e-4dd5-d2897d667254&t=3d41061b-a8e0-55f5-d2d5-8db24526eb86&l=1057

 Traceback (most recent call last):
   File "$BUILD_PREFIX/venv/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 389, in <module>
     main()
     ~~~~^^
   File "$BUILD_PREFIX/venv/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 373, in main
     json_out["return_val"] = hook(**hook_input["kwargs"])
                              ~~~~^^^^^^^^^^^^^^^^^^^^^^^^
   File "$BUILD_PREFIX/venv/lib/python3.13/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 175, in prepare_metadata_for_build_wheel
     return hook(metadata_directory, config_settings)
   File "$BUILD_PREFIX/venv/lib/python3.13/site-packages/setuptools/build_meta.py", line 374, in prepare_metadata_for_build_wheel
     self.run_setup()
     ~~~~~~~~~~~~~~^^
   File "$BUILD_PREFIX/venv/lib/python3.13/site-packages/setuptools/build_meta.py", line 317, in run_setup
     exec(code, locals())
     ~~~~^^^^^^^^^^^^^^^^
   File "<string>", line 19, in <module>
   File "$BUILD_PREFIX/venv/lib/python3.13/site-packages/torch/__init__.py", line 408, in <module>
     _load_global_deps()
     ~~~~~~~~~~~~~~~~~^^
   File "$BUILD_PREFIX/venv/lib/python3.13/site-packages/torch/__init__.py", line 364, in _load_global_deps
     raise err
   File "$BUILD_PREFIX/venv/lib/python3.13/site-packages/torch/__init__.py", line 312, in _load_global_deps
     ctypes.CDLL(global_deps_lib_path, mode=ctypes.RTLD_GLOBAL)
     ~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   File "$BUILD_PREFIX/lib/python3.13/ctypes/__init__.py", line 390, in __init__
     self._handle = _dlopen(self._name, mode)
                    ~~~~~~~^^^^^^^^^^^^^^^^^^
 OSError: $BUILD_PREFIX/venv/lib/python3.13/site-packages/torch/lib/libtorch_global_deps.so: cannot open shared object file: No such file or directory
 error: subprocess-exited-with-error

Need to figure out how to get aarch64 to build on cross-compile mode somehow.

Try to fix `OSError: $BUILD_PREFIX/venv/lib/python3.13/site-packages/torch/lib/libtorch_global_deps.so: cannot open shared object file: No such file or directory`.
@weiji14
Copy link
Copy Markdown
Member

weiji14 commented Sep 19, 2025

Ok fixed the libtorch_global_deps.so: cannot open shared object file: No such file or directory error in commit bb020d5. Builds run fine now, just some tests failing now on linux-aarch64 due to a missing runtime dependency:

Error:   × Test failed: failed to setup test environment: Cannot solve the request
  │ because of: mamba-ssm ==2.2.5 py312h2fba0ae_2 cannot be installed because
  │ there are no viable options:
  │ └─ mamba-ssm 2.2.5 would require
  │    └─ causal-conv1d >=1.5.2, for which no candidates were found.
  │ The following packages are incompatible
  │ └─ mamba-ssm ==2.2.5 py312h2fba0ae_2 cannot be installed because there are
  │ no viable options:
  │    └─ mamba-ssm 2.2.5 is excluded because due to strict channel priority
  │ not using this option from: 'file:///home/conda/feedstock_root/
  │ build_artifacts/'

wait for conda-forge/causal-conv1d-feedstock#11, or could add a conditional to remove causal-conv1d as a runtime dependency on linux-aarch64 since it is optional.

@weiji14
Copy link
Copy Markdown
Member

weiji14 commented Sep 19, 2025

@conda-forge-admin, please restart ci

@weiji14 weiji14 marked this pull request as ready for review September 19, 2025 11:53
@weiji14 weiji14 merged commit 4faf7bd into conda-forge:main Sep 19, 2025
11 checks passed
@regro-cf-autotick-bot regro-cf-autotick-bot deleted the rebuild-cuda129-0-1_hcfdc9e branch September 19, 2025 11:54
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.

3 participants