NVIDIA / NVIDIA/TensorRT-LLM

[Bug][Installation]: `TRTLLM_USE_PRECOMPILED=1` fails sanity check with Python 3.12 bindings

Open
#9,907 1 comment 0 reactions 1 assignee View on GitHub

@hchings is already working on this.

Since Dec 11, 2025.

Installation Investigating triaged
Dominant language
Python
Stars
14.7k
Forks
2.8k
Avg merge
2d 23h
Merged PRs (30d)
489

Description

System Info

Branch: release/1.1.0rc3
Docker Image: nvcr.io/nvidia/tensorrt-llm/devel:1.1.0rc3
Python Version: 3.12

How you are installing TensorRT-LLM
TRTLLM_USE_PRECOMPILED=1 pip wheel . --no-deps --wheel-dir ./build
Description

The TRTLLM_USE_PRECOMPILED=1 flag fails to skip C++ compilation despite documentation stating it should download and extract precompiled libraries. The installation fails at the sanity check stage, even though the precompiled bindings are successfully extracted.

Root Cause

The sanity_check() function checks for:tensorrt_llm/bindings or tensorrt_llm/bindings.pyi.
However, the precompiled wheel extracts: bindings.cpython-312-x86_64-linux-gnu.so (compiled shared object)
The sanity check logic doesn't recognize the platform-specific .so file pattern, causing it to incorrectly fail even when the bindings are present.

Steps to Reproduce
1. Start devel container: `make -C docker ngc-devel_run LOCAL_USER=1 DOCKER_PULL=1`
2. Run: `TRTLLM_USE_PRECOMPILED=1 pip install -e . -v`
3. Observe sanity check failure
4. Verify bindings exist: `find . -name "bindings*.so" -type f`
Expected Behavior

Installation should succeed without requiring python3 ./scripts/build_wheel.py when TRTLLM_USE_PRECOMPILED=1 is set.

Suggested Fix

Update sanity_check() to also check for platform-specific bindings patterns like bindings.cpython-*.so or bindings*.so.

Before submitting a new issue...

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.