On Mon, Jun 23, 2014 at 12:10 PM, Ilia Mirkin <imir...@alum.mit.edu> wrote: > On Mon, Jun 23, 2014 at 1:07 PM, Aaron Watry <awa...@gmail.com> wrote: >> On my machine, ${PREFIX}/lib/vdpau contains: >> libvdpau_gallium.so.1 -> libvdpau_r600.so.1.0.0 >> libvdpau_r600.so* >> libvdpau_radeonsi.so* >> >> Note that libvdpau_gallium.so.1 is only created when I force an >> ldconfig on my system (until then, I just have >> libvdpau_[r600|radeonsi]*) >> >> For some reason, while the files are in the same place, mplayer -vo >> vdpau chokes on loading these files now. If I copy >> libvdpau_r600.so.1.0.0 to /usr/local/lib/libvdpau_r600.so, then >> mplayer (-vo vdpau) picks it up and plays without issue. Is the VDPAU >> backend loader looking in the wrong directory? > > libvdpau only loads files from a fixed location, as determined by the > --prefix you use to compile it. So if you're putting mesa into a > different prefix than libvdpau it won't work. >
Ahh, that makes some sense. My libvdpau.so is at /usr/lib/x86_64-linux-gnu/libvdpau.so, and for some reason, it's finding libvdpau_r600.so if it exists in /usr/local/lib/libvdpau_r600.so, so it looks like libvdpau might also check some fall-back paths as well as its compile-time prefix (I haven't checked the source, so not sure). For now, consider the prefix thing a non-issue caused by user confusion. I used to have my distro's vdpau mesa drivers installed, and either they renamed the package while I wasn't looking, or I removed the package and didn't remember. >> >> --Aaron >> _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev