Hello!!
I just installed cuda_10.2.89_440.33.01_linux.run on CentOS 8.0-1905.
After that in NVIDIA_CUDA-10.2_Samples, I got the following ERROR message.
Where is the include file, “nvscibuf.h”?
I also just installed cuda_10.2.89_440.33.01_linux using deb on my Dell XPS 15 9560 with ubuntu 18.04 (dualbooted with windows 10 if that matters) and faced the exact same issue.
Tried “make -k” when in the NVIDIA_CUDA-10.2_Samples folder, but still got this error:
Hello hanna, I think… “-k” means skipping some errors.
That is way you got the message,
“Target ‘all’ not remade because of errors.”
Please check each directories and there are executable files or compiled binary files.
@keizofk1f3l: I know, mostly just wanted to share that I also got the same error. And yes, all sample code I have tried so far has been executable, except for those using OpenGL. Not sure if it’s caused by this error or something else thought. Could you execute OpenGL samples?
Seems to be the case
[paulj@pjux3 stubs]$ pwd
/usr/local/cuda/lib64/stubs
[paulj@pjux3 stubs]$ ls -l libcuda.so
-rwxr-xr-x. 1 root root 47216 Nov 25 12:40 libcuda.so
[paulj@pjux3 stubs]$ ls -l libvsci*
ls: cannot access ‘libvsci*’: No such file or directory
[paulj@pjux3 stubs]$
the NvSci interop support is a new BETA feature to CUDA 10.2 and hence it’s support is limited at this time. The cudaNvSci sample that is contained in the CUDA 10.2 toolkit requires a new NvStreams development package that has, to date, not yet been released. NvStreams is a product of NVIDIA Automotive SW and is already supported in DRIVE OS aarch64 Linux on DRIVE OS 5.1.12.0 . The x86_64 support package for Nvstreams is new and is due to be released soon as a part of a future DRIVE OS release. If you are interested to obtain the upcoming release of Nvstreams support for DRIVE OS on x86_64 please register for an account at https://developer.nvidia.com/DRIVE-AGX-program
The initial release of the BETA Nvstreams x86_64 library package will be handled via https://partners.nvidia.com/ which is a credentialed access portal for automotive partners for obtaining all related DRIVE OS software.
Users who don’t have a particular concern with the above should disregard this sample code. The failure of it to build correctly at this time is expected. It does not indicate any sort of problem with the install process, GPU, or compatibility.
To work around this, please issue make -k or similar when building the sample codes on linux. This does not eliminate the failure to build this sample code, but allows the other samples which are buildable, to be properly built. This failure to build will still be indicated in a general make/build process and should be disregarded.
I won’t be able to answer further questions or future-looking questions about this at this time. This includes but is not limited to:
“what about windows?”
“what does this sample code do?”
“when will XXX be available?”
“are there any workarounds?”
“where is YYY located?”
“how can I get further information?”
General questions about DRIVE HW or SW products should be posted in the Drive section of these forums.