NVIDIA / NVIDIA/TensorRT

Cross-compilation fails in CMake with "The CMAKE_CUDA_COMPILER: /usr/local/cuda-11.4/targets/aarch64-linux/bin/nvcc is not a full path to an existing compiler tool."

Open
#2,923 4 comments 0 reactions 1 assignee View on GitHub

@rajeevsrao is already working on this.

Since May 3, 2023.

triaged
Dominant language
C++
Stars
13.4k
Forks
2.4k
Avg merge
5d 3h
Merged PRs (30d)
2

Description

Description

Cross-compilation fails with error:

"The CMAKE_CUDA_COMPILER:

/usr/local/cuda-11.4/targets/aarch64-linux/bin/nvcc

is not a full path to an existing compiler tool."

Environment

TensorRT Version: 8.4.1
NVIDIA GPU: RTX-3080
NVIDIA Driver Version: 530.30.02
CUDA Version: 11.4
CUDNN Version:
Operating System: Ubuntu 20.04
Python Version (if applicable):
Tensorflow Version (if applicable):
PyTorch Version (if applicable):
Baremetal or Container (if so, version): Docker 23.0.5

Steps To Reproduce

  • git checkout 8.4.1
  • Fix GPG key issue - Change ubuntu-cross-aarch64.Dockerfile by replacing
    RUN dpkg -i /pdk_files/cuda-repo-cross-aarch64*.deb /pdk_files/cuda-repo-ubuntu*_amd64.deb \ && apt-get update \ && apt-get install -y cuda-cross-aarch64 \ && rm -rf /var/lib/apt/lists/*
    with
    RUN dpkg -i /pdk_files/cuda-repo-cross-aarch64*.deb /pdk_files/cuda-repo-ubuntu*_amd64.deb RUN cp /var/cuda-repo-cross-aarch64-ubuntu2004-11-4-local/cuda-647817BB-keyring.gpg /usr/share/keyrings/ RUN cp /var/cuda-repo-ubuntu2004-11-4-local/cuda-A7CFCDD0-keyring.gpg /usr/share/keyrings/ RUN apt-get update \ && apt-get install -y cuda-cross-aarch64 \ && rm -rf /var/lib/apt/lists/*
  • ./docker/build.sh --file docker/ubuntu-cross-aarch64.Dockerfile --tag tensorrt-jetpack-cuda11.4
  • ./docker/launch.sh --tag tensorrt-jetpack-cuda11.4 --gpus all
  • cd $TRT_OSSPATH mkdir -p build && cd build cmake .. -DTRT_LIB_DIR=$TRT_LIBPATH -DTRT_OUT_DIR=pwd/out -DTRT_PLATFORM_ID=aarch64 -DCUDA_VERSION=11.4 CC=/usr/bin/gcc make -j$(nproc)

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.