[BUG] Fix nvrtc and nvjitlink linkage and dependencies introduced from librtcx
- Dominant language
- C++
- Stars
- 9.8k
- Forks
- 1.1k
- Avg merge
- 3d 6m
- Merged PRs (30d)
- 278
Description
librtcx is always built as a static library. It supports both dynamic and static linkage to nvrtc and nvjitlink. We need to statically link both in Spark builds, but otherwise we typically want to dynamically link them both. We must also ensure that in all non-Spark distributions we also have the necessary dependencies set up so that these libraries are available at run time. Currently I think the libcudf wheel is missing the nvrtc dependency, and I am also unsure that we are properly dynamically linking in conda/wheels.
Contributor guide
Research direction
Begin with the librtcx linkage configuration and compare Spark builds with conda and wheel packaging. Verify that Spark statically links nvrtc and nvjitlink, while non-Spark distributions dynamically link them and declare the required runtime dependencies, including nvrtc for the libcudf wheel.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, spark
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100