OS: Arch Linux $ pacman -Q mesa-vdpau mesa-vdpau 19.0.2-1 $ pacman -Ql mesa-vdpau mesa-vdpau /usr/ mesa-vdpau /usr/lib/ mesa-vdpau /usr/lib/vdpau/ mesa-vdpau /usr/lib/vdpau/libvdpau_gallium.so mesa-vdpau /usr/lib/vdpau/libvdpau_nouveau.so mesa-vdpau /usr/lib/vdpau/libvdpau_nouveau.so.1 mesa-vdpau /usr/lib/vdpau/libvdpau_nouveau.so.1.0 mesa-vdpau /usr/lib/vdpau/libvdpau_nouveau.so.1.0.0 mesa-vdpau /usr/lib/vdpau/libvdpau_r300.so mesa-vdpau /usr/lib/vdpau/libvdpau_r300.so.1 mesa-vdpau /usr/lib/vdpau/libvdpau_r300.so.1.0 mesa-vdpau /usr/lib/vdpau/libvdpau_r300.so.1.0.0 mesa-vdpau /usr/lib/vdpau/libvdpau_r600.so mesa-vdpau /usr/lib/vdpau/libvdpau_r600.so.1 mesa-vdpau /usr/lib/vdpau/libvdpau_r600.so.1.0 mesa-vdpau /usr/lib/vdpau/libvdpau_r600.so.1.0.0 mesa-vdpau /usr/lib/vdpau/libvdpau_radeonsi.so mesa-vdpau /usr/lib/vdpau/libvdpau_radeonsi.so.1 mesa-vdpau /usr/lib/vdpau/libvdpau_radeonsi.so.1.0 mesa-vdpau /usr/lib/vdpau/libvdpau_radeonsi.so.1.0.0 mesa-vdpau /usr/share/ mesa-vdpau /usr/share/licenses/ mesa-vdpau /usr/share/licenses/mesa-vdpau/ mesa-vdpau /usr/share/licenses/mesa-vdpau/LICENSE $ sudo find -L / -not \( -type d -path "/dev" -prune -o -path "/home" -prune -o -path "/media" -prune -o -path "/mnt" -prune -o -path "/proc" -prune -o -path "/root" -prune -o -path "/run" -prune -o -path "/sys" -prune -o -path "/tmp" -prune -o -path "/var" -prune \) -type l -ls 920254 0 lrwxrwxrwx 1 root root 25 Apr 12 07:07 /usr/lib64/vdpau/libvdpau_gallium.so -> libvdpau_gallium.so.1.0.0 920254 0 lrwxrwxrwx 1 root root 25 Apr 12 07:07 /usr/lib/vdpau/libvdpau_gallium.so -> libvdpau_gallium.so.1.0.0 920254 0 lrwxrwxrwx 1 root root 25 Apr 12 07:07 /lib64/vdpau/libvdpau_gallium.so -> libvdpau_gallium.so.1.0.0 920254 0 lrwxrwxrwx 1 root root 25 Apr 12 07:07 /lib/vdpau/libvdpau_gallium.so -> libvdpau_gallium.so.1.0.0 The file libvdpau_gallium.so isn't in 19.0.1-1. First I thought this was an Arch Linux packaging issue and reported it at https://bugs.archlinux.org/task/62323. But according to the bug handler it is an upstream issue, so reporting it here. Regards
My guess is that arch is using meson? I don't think this happens if you use the tried-and-true autoconf-based build.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1175.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.