I have an executable, including CUDA kernels on a Linux server, and I would like to use the Nsight Compute on my local windows system to profile the remote executable in an interactive way. As I ran profiling, I got the following message:
Launching: /scratch/bbp_algo1/ziqi/SandBox/regera-gpu/Blazer/MercuryImageComputer/KT/leaf/M31/BrightField/bin/LeafStandalone/Release/12/LeafStandAlone.x86-64 (host: 10.70.72.71)
Trying to connect to process…
Searching for attachable processes on 10.70.72.71:49152-49215…
/scratch/bbp_algo1/ziqi/SandBox/regera-gpu/Blazer/MercuryImageComputer/KT/leaf/M31/BrightField/bin/LeafStandalone/Release/12/LeafStandAlone.x86-64: error while loading shared libraries: libfftw3f.so.3: cannot open shared object file: No such file or directory
From my understanding, the profiling failed as a shared binary named “libfftw3f.so.3” cannot be found. This shared library was indeed linked to in our binary, but we had no problem running the executable on the remote server, and I am confused why in the case of Nsight Compute, it failed to find such a dynamic library, and failed profiling as a consequence. Can anyone point out how to fix the issue?