Dear,
I have some library naming question about nvidia-jetpack 4.6.2-b5
Some libraries in package (for example: nvidia-l4t-3d-core) doesn’t obey a rule that
creating a symbolic link to real library
For example:
/usr/lib/aarch64-linux-gnu/tegra/libnvidia-fatbinaryloader.so.440.18
doesn’t have a symbolic link as :
/usr/lib/aarch64-linux-gnu/tegra/libnvidia-fatbinaryloader.so
or
/usr/lib/aarch64-linux-gnu/tegra/libnvidia-fatbinaryloader.so.440
But some package create the symbolic link, like:
root@localhost:/usr/lib/aarch64-linux-gnu/tegra# dpkg -L nvidia-l4t-cuda
/.
/usr
/usr/lib
/usr/lib/aarch64-linux-gnu
/usr/lib/aarch64-linux-gnu/tegra
/usr/lib/aarch64-linux-gnu/tegra/libcuda.so.1.1
/usr/share
/usr/share/doc
/usr/share/doc/nvidia-l4t-cuda
/usr/share/doc/nvidia-l4t-cuda/copyright
/usr/share/doc/nvidia-l4t-cuda/changelog.Debian.gz
/usr/lib/aarch64-linux-gnu/libcuda.so
/usr/lib/aarch64-linux-gnu/tegra/libcuda.so
It’s a puzzle for the developer, because attention should be payed to link the full name of library, and should modified for further update.
Any comments or suggestions are welcome,
Best Regards,