/snap/rocm-validation-suite/current/opt/rocm-6.3.3/bin/rvs: error while loading shared libraries: libyaml-cpp.so.0.8: cannot open shared object file: No such file or directory
According to the errors they get when the RVS test runs on 22.04, it fails because it can't find libyaml-cpp0.8
Looking at the snapcraft.yaml that library is staged, and when I look at the snap installed locally that lib is contained in the snap directory:
bladernr@rocinante:~/development/checkbox/providers/gpgpu$ find /snap/rocm-validation-suite/ -name "libyaml-cpp*"
/snap/rocm-validation-suite/16/usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.8
/snap/rocm-validation-suite/16/usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.8.0
/snap/rocm-validation-suite/16/usr/share/doc/libyaml-cpp0.8
I installed the rocm-validation-suite snap locally and when I try ldd, it seems that despite the library being included in the snap, the tool is actually still looking on the main filesystem for that library:
bladernr@rocinante:~/development/checkbox/providers/gpgpu$ ldd /snap/rocm-validation-suite/current/opt/rocm-6.3.3/bin/rvs | grep yaml
libyaml-cpp.so.0.8 => not found
If I install libyaml-cpp0.8 locally via deb, that puts it in the system path and rvs can find it now:
bladernr@rocinante:~/development/checkbox/providers/gpgpu$ ldd /snap/rocm-validation-suite/current/opt/rocm-6.3.3/bin/rvs | grep yaml
libyaml-cpp.so.0.8 => /lib/x86_64-linux-gnu/libyaml-cpp.so.0.8 (0x00007e66cb38d000)
so there is some path issue there. I wonder if that has something to do with --devmode letting it look on the system path instead of inside the snap? or maybe there's some way to force it to include the path in the snap so that the library is found?
Note, they saw this on 22.04, but I see the same issues with the library on 25.10 as well (cant run the test since my system doesn't have an AMD GPU, but I can at least check the shared library stuff locally.
According to the errors they get when the RVS test runs on 22.04, it fails because it can't find libyaml-cpp0.8
Looking at the snapcraft.yaml that library is staged, and when I look at the snap installed locally that lib is contained in the snap directory:
I installed the rocm-validation-suite snap locally and when I try ldd, it seems that despite the library being included in the snap, the tool is actually still looking on the main filesystem for that library:
If I install libyaml-cpp0.8 locally via deb, that puts it in the system path and rvs can find it now:
so there is some path issue there. I wonder if that has something to do with --devmode letting it look on the system path instead of inside the snap? or maybe there's some way to force it to include the path in the snap so that the library is found?
Note, they saw this on 22.04, but I see the same issues with the library on 25.10 as well (cant run the test since my system doesn't have an AMD GPU, but I can at least check the shared library stuff locally.