On Sat, 25 Oct 2014 14:50:26 +0200 Heinz Wiesinger <ppr...@liwjatan.at> wrote:
> On Saturday 25 October 2014 08:42:01 John Vogel wrote: > > On Sat, 25 Oct 2014 13:47:40 +0200 > > > > Heinz Wiesinger <ppr...@liwjatan.at> wrote: > > > On Saturday 25 October 2014 00:03:37 John Vogel wrote: > > > > The SlackBuilds for libva and vdpau-video are based on very old > > > > versions. I > > > > have had good success building libva-1.4.0, though it won't build > > > > without > > > > wayland or possibly with this hack I found: > > > > https://www.libreoffice.org/bugzilla/show_bug.cgi?id=79478#c6 . I have > > > > got > > > > a SlackBuild for libva-vdpau-driver at version 0.7.4 based on > > > > archlinux's > > > > libva-vdpau-driver hacked over the top of the old vdpau-video > > > > SlackBuild. I > > > > can forward my scripts or make them available on my github repo, or > > > > both. > > > > Both builds work well here on two of my systems with nvidia boards in > > > > them. > > > > > > I have patches to circumvent the bug. I created them for 1.3.1, but they > > > should work just the same for 1.4, maybe with small modifications. They > > > are not really suitable upstream fixes, which is why I didn't bother > > > attaching them to the bug report at fd.o. I'll attach them here in case > > > anyone is interested. Note that libva-intel-driver needs a small > > > additional hack in one Makefile to> > > > make it compile: > > > > sed -ie "1266d" src/Makefile > > > > > > Grs, > > > Heinz > > > > Thank you! > > > > I can comfirm that the libva patch applies to 1.4.0 and 1.4.1, both > > of which build without wayland and wayland-scanner when given the > > --enable-wayland=0 configure argument. > > > > The libva-intel-driver patch applies to 1.4.0 and 1.4.1, but there is a bug > > in the file generation of src/Makefile (even for 1.3.2) that causes `make` > > to bomb. Shouldn't be hard to fix... I'll post it when I get it working, and > > can supply a libva-intel-driver slackbuild for testing (I don't have any > > Intel cpus/gpus at home, or I would test it myself). > > That's what the sed command in my previous mail was for :) > > Grs, > Heinz Ah, I read it, but forgot all about it when I was hacking the slackbuild together. Must be a leak in my brain, or early senility setting in. Thanks again. Cheers, John _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
