Skip to content

wheels: build with oldest CUDA 13 CTK (13.0.x) #257

@jameslamb

Description

@jameslamb

Description

In mid-26.04, RAPIDS was building its wheels with v13.1.1 of the CUDA toolkit (including libnvJitLink 13.1.1) and directly linking against libnvJitLink for JIT-LTO (example: rapidsai/cuvs#1405).

This resulted in runtime issues in environments with v13.0.x of the CTK, like this:

libcugraph.so: undefined symbol: __nvJitLinkGetErrorLog_13_1, version libnvJitLink.so.13

Requiring nvidia-nvjitlink>=13.1 at runtime would solve those issues, but it'd also make RAPIDS wheels incompatible with cuda-toolkit[nvjitlink]<13.1, which torch 2.10 (the latest release) pins to:

In an offline discussion with @bdice @vyasr and @divyegala we discussed and tried several options (example: rapidsai/cuvs#1855), and decided to try building RAPIDS wheels against CTK 13.0.x for RAPIDS 26.04, to avoid losing compatibility with projects tightly pinned to earlier nvJitLink versions.

This tracks that work.

Benefits of this work

  • allows RAPIDS to continue adopting JIT-LTO while also staying compatible with torch and other projects tightly pinning to earlier nvidia-nvjitlink versions

Acceptance Criteria

  • all RAPIDS libraries build wheels against CTK 13.0
  • RAPIDS conda builds continue to build against the latest CUDA 13 CTK RAPIDS supports (as of this writing, 13.1.1)
  • RAPIDS devcontainers continue to support the latest CUDA 13 CTK RAPIDS supports
  • RAPIDS CUDA 12 wheels continue to build against the latest CUDA 12 CTK RAPIDS support (as of this writing, 12.9.1)
  • cugraph-gnn wheels CI is successfully testing against CUDA 12 and CUDA 13 torch wheels

Approach

Notes

N/A

Metadata

Metadata

Assignees

Labels

breakingIntroduces a breaking changeimprovementImproves an existing functionality

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions