From: Marco van Hulten <marco@hulten.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: libvdpau: cannot open shared object
Date: Sat, 16 Dec 2017 09:08:53 +0100 [thread overview]
Message-ID: <20171216090853.599b7169@jasniac.instanton> (raw)
In-Reply-To: <877etohxku.fsf@gnu.org>
Ludovic—
Je 15 dec 15:31 skribis Ludovic:
> Efraim Flashner <efraim@flashner.co.il> skribis:
>
> > $ VDPAU_DRIVER=va_gl LD_LIBRARY_PATH=$(guix build libvdpau-va-gl)/lib 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
>
> Well the exact line is this:
>
> VDPAU_DRIVER=va_gl \
> LD_LIBRARY_PATH=$(./pre-inst-env guix build libvdpau-va-gl)/lib/vdpau \
> $(guix build vdpauinfo)/bin/vdpauinfo
>
> Works for me! It displays lots of things. :-)
> [...]
It does not work for me, still cannot find 'libvdpau_va_gl.so'.
I am trying to understand the commands that you use to define
LD_LIBRARY_PATH:
kodi@watson ~$ guix build libvdpau-va-gl
guix build: error: libvdpau-va-gl: unknown package
kodi@watson ~$ guix build vdpauinfo
/gnu/store/46x8ba3q11zgq8qygqpgkv41ws9km9b1-vdpauinfo-1.0
Where can I find 'pre-inst-env'? Does this make guix aware of the
libvdpau-va-gl package?
I'm running GuixSD 0.14.0 on real hardware, and did a pull and upgrade
just yesterday.
—Marco
next prev parent reply other threads:[~2017-12-16 8:09 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
2017-12-15 12:18 ` Efraim Flashner
2017-12-15 14:31 ` Ludovic Courtès
2017-12-16 8:08 ` Marco van Hulten [this message]
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=20171216090853.599b7169@jasniac.instanton \
--to=marco@hulten.org \
--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).