From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: New packages: libnvidia-container-1.0.5 and nvidia-container-runtime-…
Date: Thu, 02 Jan 2020 10:00:42 +0100 [thread overview]
Message-ID: <20200102090042.nsCwzuwHHHFinX6pxjikAs4Z3DIAp1Y497TCS6i67zU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17505@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
New comment by shaeri on void-packages repository
https://github.com/void-linux/void-packages/pull/17505#issuecomment-570148966
Comment:
Thanks for testing the packages.
Creating the symlink is correct and usually libfoo.so and libfoo.so.1 are symlinks to the libfoo..so.version. ldconfig usually takes care of creating the symlinks. That is part of what ldconfig does. So after installing the nvidia drivers (nvidia440.44) you should run ldconfig as sudo user and it will take care of creating all the symlinks.
`sudo ldconfig`
The issue here is that libnvoptix is part of the nvidia driviers and somehow the symlinks to libnvoptix.so and libnvoptix.so.1 are not created as part of driver installation. The nvidia drivers are not part of the free void-linux repos and furthermore installing them without creating the correct xorg.conf may break the display, therfore, I opted for not including them to be installed alongside these 2 packages.
I can include the last step of running ldconfig as a post installation step. However, if nvidia drivers are installed after these 2 packages, this problem will persist.
next prev parent reply other threads:[~2020-01-02 9:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17505@inbox.vuxu.org>
2020-01-02 3:25 ` New packages: libnvidia-container-1.0.5 and nvidia-container-runtime-… voidlinux-github
2020-01-02 3:26 ` voidlinux-github
2020-01-02 9:00 ` voidlinux-github
2020-01-02 9:00 ` voidlinux-github [this message]
2020-01-02 9:01 ` voidlinux-github
2020-01-02 9:02 ` voidlinux-github
2020-12-13 18:38 ` vixus0
2021-11-03 0:59 ` subtlevenom
2022-04-15 2:13 ` github-actions
2022-04-29 2:13 ` [PR PATCH] [Closed]: " github-actions
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200102090042.nsCwzuwHHHFinX6pxjikAs4Z3DIAp1Y497TCS6i67zU@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).