For @??? (there are actually two conversations in the thread)…
Are you cross compiling or native compile on the Jetson? I assume native on the Jetson, just checking.
I downloaded riffa 2.1 and am examining its Makefile. Notice in “source/driver/linux/Makefile” that it uses “uname -r”. If you cross compile this is not correct (the host uname would mistakenly be used instead of Jetson uname), but should be ok for native build (be sure “uname -r” is “3.10.96-tegra” prior to starting build…FYI, you might also consider first upgrading to R28.1 which has a 4.x kernel).
This driver also looks at “/etc/redhat-release”. Then this block is used in the Makefile:
if [ -f "$(RHR)" ]; then yum install kernel-devel-`uname -r`;\
else apt-get install linux-headers-`uname -r`; fi
Since there is no redhat-release, it installs linux-headers package over the internet and wants “linux-headers-3.10.96-tegra”, but this doesn’t exist in default repositories. You could place the headers there yourself, e.g., just via a symbolic link to the kernel source’s headers as distributed by NVIDIA. Had the public repo for linux-headers succeeded, then possibly it differs from the NVIDIA supplied kernel anyway…not sure on that. Comment that block out, then verify if there are already files in “/usr/include/linux/” (I already have this, but it could have been from another package you didn’t install…check). Completely commenting out that block in the Makefile mentioned above will be correct it if you have headers already.
The actual headers are at “/usr/src/linux-headers-$(uname -r)/” and are part of the L4T install (this directory is not owned by a package, it is a direct file addition). Verify you have this directory, then find out if this symbolic link points there:
ls -ld /lib/modules/$(uname -r)/build
If not, then you can add a symbolic link (don’t do this if link is already valid):
sudo ln -sf /usr/src/linux-headers-$(uname -r) /lib/modules/$(uname -r)/build
Run a make clean, then try to build again and see how far it gets.