Missing CUDA pkgconfig .pc files (cudart-10.2.pc and cuda-10.2.pc) DRIVE OS 5.2.0

Please provide the following info (check/uncheck the boxes after clicking “+ Create Topic”):
Software Version
[*] DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other

Target Operating System
[*] Linux
QNX
other

Hardware Platform
[*] NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
[*] 1.4.0.7363
other

Host Machine Version
[*] native Ubuntu 18.04
other

Hi,

I have recently flashed the DRIVE OS 5.2.0 on my DRIVE AGX Xavier platform. Previosuly I was using DRIVE SW 10 Linux.

I noticed that on this new DRIVE OS 5.2.0 release the CUDA pkgconfig .pc files (cudart-10.2.pc and cuda-10.2.pc) are missing in the DRIVE AGX Xavier platform after flashing.

I verified If I had the packages installed with "apt search cuda" command and effectively at least the cudart-10-2 and cuda-libraries-10-2 packages are installed, as shown below:

cuda-cudart-10-2/now 10.2.187-1 arm64 [installed,local]
  CUDA Runtime native Libraries

cuda-libraries-10-2/now 10.2.187-1 arm64 [installed,local]
  CUDA Libraries 10.2 meta-package

cuda-license-10-2/now 10.2.187-1 arm64 [installed,local]
  CUDA licenses

On my project based on meson, I used the .pc files to verify the package’s dependencies. Now it is failing to configure because it doesn´t find the .pc files for CUDA dependency.

Before upgrading to DRIVE OS 5.2.0 I was using DRIVE SW 10 without any problem. On DRIVE SW 10 the cudart-10.2.pc and cuda-10.0.pc were found after CUDA installation on the DRIVE AGX platform without any issue.

Could you please help with this issue?

Thanks in advance for any help.

Best regards,
-Daniel

Dear @dgarba,
Looks like you already filed a relavant topic at How to install cuda-toolkit on DRIVE OS 5.2.0 DRIVE AGX platform?. Could you continue the discussion on the same thread.

BTW do you need CUDA 10.2 toolkit on target to compile any package or your build just check if CUDA is present on the target using these hints? If it uses them as a hint, could you check copying those files manually to by pass build error? Because all required CUDA libs are present on target.

Hi @SivaRamaKrishnaNV,

I need CUDA 10.2 toolkit on target to compile my package, that’s why my build first check if CUDA is presently using the pkg-config (.pc) files. I could copy manually those .pc files, but then my package build will fail due to missing CUDA headers during compilation. And effectively, the CUDA header files are not present on the target on DRIVE OS 5.2.0.

I am not sure if that is a bug on this release, but I will expect that any package installed in the system has its respective pkg-config (.pc) file, as it is the standard, at least for apt installed packages.

Best regards,
-Daniel

Dear @dgarba,
Thank you. We have raised this issue to team already and working on it to avoid such issues.
Could you manually copy the headers to by pass the build error.