[elrepo] EL6 fglrx devel packages?

[Phil Perry]

On 18/05/12 03:05, Andy wrote:
> Phil Perry wrote:
>> On 17/05/12 08:32, Andy wrote:
>>> I can't see the fglrx devel packages in the 'elrepo' EL6 repo, despite the
>>> SRPM contains the config for them, how come they are missing?
>>>
>>
>> Hi Andy,
>>
>> No one ever requested them so they were never released.
>>
>> I've pushed the devel packages for the last two releases (versions 12.1
>> and 12.3) for el5 / el6 to the repos. These should appear on the mirrors
>> shortly.
>>
>> I'll make sure new versions are released going forward. Is that OK for you?
>
> That's ok, thanks. I had been puzzled as to why they where missing rather than
> actually missing them myself (as I can always build them from the SRPM).
>

Great.

> Anyway, I was also wondering if you are interested in adding the fglrx VA-API
> backend package to Elrepo, since you have libva and you have the fglrx drivers
> but not the missing link between them.
>

I'm not an ATI/AMD fglrx user. Is VA-API similar to VDPAU on the nvidia 
platform?

Phil S. packaged libva in our extras repo for el6 to support his updated 
Intel Xorg drivers.

Anyway, I don't see any reason why we couldn't include this in elrepo.

> I have built the package, and it works fine with VLC 2.0.x from my repo
> ( pkgrepo.linuxtech.net/el6/ ),

Great - then as you have done the hard work, why don't I invite you to 
officially maintain the package in elrepo. Would you be willing to do that?

We would also be really interested to hear from anyone willing to 
maintain the fglrx packages too!

> there is just one obscure bug that I can't
> pinpoint (I found a workaround for it but not the source of the bug).
>
> Basically when running vainfo or vlc or presumably any other vaapi client
> while using the vxba (fglrx) backend, it attempts to look for libAMDXvBA.cap
> in /usr/lib/ (even on x86_64!) rather than %{_libdir}/fglrx/. I cannot figure
> out where this has been hardcoded!
>
> For now I have added a simple workaround by sym-linking:
>
> /usr/lib/libAMDXvBA.cap ->  %{_libdir}/fglrx/libAMDXvBA.cap
>
> Which solves the issue but of course it's an ugly hack.
>

If it works for now... :-)

> You can find my current spec file here:
> http://pkgrepo.linuxtech.net/el6/workinprogress/spec-files/libva-driver-xvba.spec
>
> and the SRPM:
> http://pkgrepo.linuxtech.net/el6/workinprogress/source/libva-driver-xvba-0.8.0-5.src.rpm
>
> I have tested this using libva-1.0.15 from my repo (should be compatible with
> the same package from Elrepo) and fglrx-x11-drv-12.3-1 from Elrepo.
>

What about el5? Can (should?) we do this for el5 too?

> You can repoduce the bug I mentioned earlier by removing the above mentioned
> symlink and then running 'strace vainfo'. You will see that it fails on the
> missing /usr/lib/libAMDXvBA.cap.
> In case you figure out the source of this bug please let me know too!
>
> It would be great if we could stay compatible with regards to these packages
> (libva, libva-driver-xvba) as the Elrepo and the Linuxtech repos currently
> complement each other quite well and it would be great to keep it that way. :)
>

Well, perhaps the best way to ensure that is if the same person 
maintains them in both repos :-)

One of the biggest issues we have is that we often don't have the 
hardware to test the packages we are maintaining. It's always best if 
the package maintainer has a vested interest and is actually using the 
packages.

Regards,

Phil