> "JJ" == James Jones writes:
JJ> The correct dir is /vdpau. From here:
So it /is/ installed where it is supposed to be.
JJ> Do you have an older libvdpau.so?
x11-libs/libvdpau-0.4.1.
So this is a bug in the ebuild. It configured module-dir to correctly
choose from /usr/lib{,32,64,x32}
On Fri, Dec 16, 2011 at 7:38 PM, James Jones wrote:
> On 12/16/11 4:27 PM, Younes Manton wrote:
>>
>> On Fri, Dec 16, 2011 at 7:01 PM, James Cloos wrote:
>>>
>>> I've been trying to test out vdpau w/o success.
>>>
>>> It turns out that libvdpau_r600.so is in /usr/lib64/vdpau/, whereas
>>> everyth
On 12/16/11 4:27 PM, Younes Manton wrote:
On Fri, Dec 16, 2011 at 7:01 PM, James Cloos wrote:
I've been trying to test out vdpau w/o success.
It turns out that libvdpau_r600.so is in /usr/lib64/vdpau/, whereas
everything looks for it in the standard ld path (ie, /usr/lib64).
With »ln -s vdpau
On Fri, Dec 16, 2011 at 7:01 PM, James Cloos wrote:
> I've been trying to test out vdpau w/o success.
>
> It turns out that libvdpau_r600.so is in /usr/lib64/vdpau/, whereas
> everything looks for it in the standard ld path (ie, /usr/lib64).
>
> With »ln -s vdpau/libvdpau_r600.so /usr/lib64/« it s
I've been trying to test out vdpau w/o success.
It turns out that libvdpau_r600.so is in /usr/lib64/vdpau/, whereas
everything looks for it in the standard ld path (ie, /usr/lib64).
With »ln -s vdpau/libvdpau_r600.so /usr/lib64/« it seems to work.
Is mesa wrong to install the libs to ${libdir}/v
