docs: Jetson build prerequisites omit the NVRTC headers (cuda-nvrtc-dev) and the TensorRT plugin headers
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- cmake, cpp, linux
- Domain
- build-system, documentation
Research direction
The Jetson package list is in docs/source/user_guide/getting_started/installation.md around lines 39-44, under the source workflow for the C++ runtime. The NVRTC requirement is enforced in cmake/FindNVRTC.cmake (lines 112-117), and cpp/plugins/qsaAttentionPlugin/qsaAttentionPlugin.h:20 includes NvInferPlugin.h. Start by adding cuda-nvrtc-dev-13-2 and libnvinfer-headers-plugin-dev to the Jetson install step, with the CUDA suffix matching JetPack. Done means the step lists both packages and a runtime note for cuda-nvrtc-13-2 is included.
Written by the indexing model from the issue text.
Description
Describe the bug
The installation guide's package step for Jetson installs only cmake, build-essential and git (docs/source/user_guide/getting_started/installation.md:39-44 at 0f52705). Two more packages are required to build on JetPack 7.2 and are not mentioned:
cuda-nvrtc-dev-13-2.cmake/FindNVRTC.cmake:112-117is fatal withoutnvrtc.h:
The message points at CMake variables; the fix on a device is one apt package. My Jetson Orin NX on JetPack 7.2 did not have the header until I installed it. I have not checked a freshly flashed image, so I do not know whether a default JetPack install includes it.Plugin build-time NVRTC JIT requires nvrtc.h and libnvrtc.so or libnvrtc_static.a. Set NVRTC_ROOT_DIR or CUDA_DIR/CUDA_TARGET_DIR to a CUDA Toolkit with NVRTC.libnvinfer-headers-plugin-dev.cpp/plugins/qsaAttentionPlugin/qsaAttentionPlugin.h:20includes<NvInferPlugin.h>, which lives in that package, not inlibnvinfer-dev. A full JetPack image gets it through thetensorrt-devmetapackage; a minimal install (for example a container built from the Jetson apt repository withlibnvinfer-devonly) stops at
Nothing linkscpp/plugins/qsaAttentionPlugin/qsaAttentionPlugin.h:20: fatal error: NvInferPlugin.h: No such file or directorylibnvinfer_plugin; the header alone is needed.
Impact: nice to have; each costs a failed configure or compile and a search.
Steps/Code to reproduce bug
- On a JetPack 7.2 Jetson Orin without
cuda-nvrtc-dev-13-2installed (dpkg -l cuda-nvrtc-dev-13-2), follow installation.md "Source workflow: C++ runtime" steps 1-4 as written. cmakestops with the NVRTC error above.sudo apt install cuda-nvrtc-dev-13-2fixes it.- In a minimal environment with
libnvinfer-devbut withouttensorrt-dev,makestops at theNvInferPlugin.herror.sudo apt install libnvinfer-headers-plugin-devfixes it.
Build configuration:
cmake .. -DCMAKE_BUILD_TYPE=Release -DTRT_PACKAGE_DIR=/usr -DCMAKE_TOOLCHAIN_FILE=cmake/aarch64_linux_toolchain.cmake -DEMBEDDED_TARGET=jetson-orin -DCUDA_CTK_VERSION=13.2 -DENABLE_CUTE_DSL=ALL
Runtime command used:
# not applicable: configure/compile time
Expected behavior
Step 1 of the Jetson instructions lists the two packages (with the CUDA version suffix matching the JetPack release), and ideally the FindNVRTC.cmake fatal message names cuda-nvrtc-dev-<ver> for Jetson. I can open a small docs PR once this is approved.
System information (Edge Device)
- Platform (e.g., NVIDIA Jetson Thor): NVIDIA Jetson Orin NX 16 GB (header gap also reproduced in an aarch64 container built from the Jetson r39.2 apt repository)
- Software release (e.g., JetPack 7.1): JetPack 7.2 (L4T R39.2)
- CPU architecture: aarch64
- GPU compute capability (e.g., SM110 for Jetson Thor): SM87
- Total device memory: 16 GB (unified)
- Build type (e.g., Release, Debug): Release
- Library versions:
- TensorRT Edge-LLM version or commit hash: 0f52705 (docs and cmake read at this commit); the NVRTC gap was hit building 0.10.1 on the device
- CUDA: 13.2 (cuda-nvrtc-dev-13-2 13.2.86-1)
- TensorRT: 10.16.2 (libnvinfer-headers-plugin-dev 10.16.2.10-1+cuda13.2)
- C++ compiler (e.g., GCC 11.4): GCC 13.3.0
- CMake options used:
- CMAKE_TOOLCHAIN_FILE: cmake/aarch64_linux_toolchain.cmake
- EMBEDDED_TARGET: jetson-orin
- TRT_PACKAGE_DIR: /usr
- Any other details that may help: the built plugin links
libnvrtc.so.13at run time, so the runtime packagecuda-nvrtc-13-2is needed on deployment devices as well; a sentence on that would help users who copybuild/to another device.
- Dominant language
- Python
- Stars
- 590
- Forks
- 143
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/TensorRT-Edge-LLM
-
llm_inference ignores temperature/top_p/top_k from the input JSON its own help tells you to set them inPossibly taken @filipemartinsubrobotics claimed this 36 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
NVIDIA/TensorRT-Edge-LLM#211 · 2 comments ·
Maintainers usually reply within 5 days
-
fix: Jetson Orin + JetPack 6.2 (CUDA 12.6, listed as Compatible platform) fails to build with ENABLE_CUTE_DSL=ALL — missing cudaLibrary_t compat shim in cuteDslF16MoeRunner.hPossibly taken @mihai-chiorean claimed this 9 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NVIDIA/TensorRT-Edge-LLM#183 · 4 comments · 1 reaction ·
Maintainers usually reply within 5 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NVIDIA/TensorRT-Edge-LLM#165 · 2 comments ·
Maintainers usually reply within 5 days
-
[Bug][Export]: checkpoint loader can replace declared FP16/BF16 parameters with FP32 tensorsPossibly taken @suharvest claimed this 86 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NVIDIA/TensorRT-Edge-LLM#144 · 1 comment ·
Maintainers usually reply within 5 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
NVIDIA/TensorRT-Edge-LLM#125 · 1 comment ·
Maintainers usually reply within 5 days
All issues in NVIDIA/TensorRT-Edge-LLM
Similar issues
-
debt
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/vscode-flake8#601 ·
Maintainers usually reply within 1 day
-
nonews refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Uninett/nav#4255 · 1 comment · 1 reaction ·
Maintainers usually reply within 3 days
-
namespace operations
Difficulty 1/5 Under an hour Newbie friendliness 70/100
EclipseFdn/open-vsx.org#14421 ·
Maintainers usually reply within 1 day
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ubuntu/ubuntu-project-docs#850 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day