From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: libvdpau: cannot open shared object
Date: Fri, 15 Dec 2017 08:38:55 +0200 [thread overview]
Message-ID: <20171215063855.GA1457@macbook41> (raw)
In-Reply-To: <876099u187.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 3494 bytes --]
On Thu, Dec 14, 2017 at 10:07:20AM +0100, Ludovic Courtès wrote:
> Hi!
>
> Efraim Flashner <efraim@flashner.co.il> skribis:
>
> > On Tue, Dec 12, 2017 at 05:44:43PM +0100, Ludovic Courtès wrote:
>
> [...]
>
> >> I searched for “libvdpau_i965.so” on the intertubes and it seems to be a
> >> problem “everyone has.” For instance:
> >>
> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869815
> >>
> >> So it seems that we lack a driver package.
> >>
> >> Ludo’.
> >
> > here's a patch for libvdpau-va-gl. after setting 'VDPAU_DRIVER=va_gl'
> > and running 'guix environment --ad-hoc libvdpau-va-gl vdpauinfo -- vdpauinfo'
> > I get:
> > display: :0.0 screen: 0
> > Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
> > Error creating VDPAU device: 1
> > so it still needs some more work
>
> What if you point LD_LIBRARY_PATH to libvdpau-va-gl?
>
> > From da659401a0116d0810f003769c933253f5b18f4c Mon Sep 17 00:00:00 2001
> > From: Efraim Flashner <efraim@flashner.co.il>
> > Date: Tue, 12 Dec 2017 21:44:49 +0200
> > Subject: [PATCH] gnu: Add libvdpau-va-gl.
> >
> > * gnu/packages/video.scm (libvdpau-va-gl): New variable.
> > * gnu/packages/patches/libvdpau-va-gl-unbundle.patch: New file.
> > * gnu/local.mk (dist_patch_DATA): Register it.
>
> [...]
>
> > + (native-inputs
> > + `(("libvdpau" ,libvdpau)
>
> Should move to ‘inputs’ I guess?
>
> Otherwise LGTM, thanks for acting this fast!
$ guix gc --references $(guix build libvdpau-va-gl)
/gnu/store/1zfmi6bixxz3fljr4kfy37xpjial90p1-libva-1.8.3
/gnu/store/3h31zsqxjjg52da5gp3qmhkh4x8klhah-glibc-2.25
/gnu/store/6wyjls0q2c9gjskkplsr1ad09p3d8gzg-gcc-5.4.0-lib
/gnu/store/7mdyg1vigcxqb1ra16mdqnhz8aa00xc7-libxext-1.3.3
/gnu/store/8z7130mb33a3jqliqs6bq2d46mar5gqy-mesa-17.2.1
/gnu/store/d3pbj6vynkig0v0lnwp9nh04sijxin2w-libvdpau-va-gl-0.4.2
/gnu/store/p37m873k9k69m944njar80i6bsmqrcvj-libx11-1.6.5
libvdpau is actually a propagated input of mesa
>
> When we have that, we can at least arrange for things to work
> out-of-the-box on GuixSD. It’s better if we can do that without setting
> LD_LIBRARY_PATH, we’ll have to investigate how this can be done. At
> least, we’ll have to set VDPAU_DRIVER=va_gl I presume?
>
> Thanks,
> Ludo’.
From the upstream documentation VDPAU_DRIVER=va_gl is the minimum needed
to get it working, and then there are a couple of other environmental
variables that can be set to change its behavior.
$ VDPAU_DRIVER=va_gl LD_LIBRARY_PRELOAD=$(guix build libvdpau-va-gl) env | grep VDPAU
VDPAU_DRIVER=va_gl
$ VDPAU_DRIVER=va_gl LD_LIBRARY_PRELOAD=$(guix build libvdpau-va-gl) vdpauinfo
display: :0.0 screen: 0
Failed to open VDPAU backend libvdpau_va_gl.so: cannot open shared object file: No such file or directory
Error creating VDPAU device: 1
Not so helpful to us, but upstream wants us to install it in the same
directory as the other vdpau*so files. I suppose we could add a
mesa-headers package and use that to build it and then just copy it into
mesa-out/lib/vdpau, but I really don't like that idea. I'm inclined to
push it as is and then we'll work out exactly how to make it work for
us.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-15 6:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-10 14:14 libvdpau: cannot open shared object Marco van Hulten
2017-12-10 14:30 ` ng0
2017-12-10 15:04 ` Marco van Hulten
2017-12-10 20:08 ` Efraim Flashner
2017-12-12 16:44 ` Ludovic Courtès
2017-12-12 19:58 ` Efraim Flashner
2017-12-14 9:07 ` Ludovic Courtès
2017-12-15 6:38 ` Efraim Flashner [this message]
2017-12-15 11:02 ` Ludovic Courtès
2017-12-15 12:18 ` Efraim Flashner
2017-12-15 14:31 ` Ludovic Courtès
2017-12-16 8:08 ` Marco van Hulten
2017-12-16 19:00 ` Ricardo Wurmus
2017-12-16 17:05 ` Efraim Flashner
2017-12-18 20:40 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171215063855.GA1457@macbook41 \
--to=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).