From: ludo@gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim@flashner.co.il>
Cc: help-guix@gnu.org
Subject: Re: libvdpau: cannot open shared object
Date: Fri, 15 Dec 2017 12:02:14 +0100 [thread overview]
Message-ID: <876098jlu1.fsf@gnu.org> (raw)
In-Reply-To: <20171215063855.GA1457@macbook41> (Efraim Flashner's message of "Fri, 15 Dec 2017 08:38:55 +0200")
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Thu, Dec 14, 2017 at 10:07:20AM +0100, Ludovic Courtès wrote:
[...]
>> > 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
OK.
>> 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
It should be:
LD_LIBRARY_PATH=$(guix build libvdpau-va-gl)/lib
or:
LD_PRELOAD=$(guix build libvdpau-va-gl)/lib/libwhatever-its-called.so
HTH!
Ludo’.
next prev parent reply other threads:[~2017-12-15 11:02 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
2017-12-15 11:02 ` Ludovic Courtès [this message]
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=876098jlu1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=efraim@flashner.co.il \
--cc=help-guix@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).