From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: mesa-ati-dri-32bit does not provide ICD File
Date: Sun, 16 Jun 2019 09:16:59 +0200 [thread overview]
Message-ID: <20190616071659.xEYWJbN4Y6_QqD2Du0ZBIUtBmgHDwjtgFMUiOQk7oSk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-3293@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/issues/3293#issuecomment-502427757
Comment:
Question to myself, is lib32 an existant folder/symlink on i686 Void, if yes fixing this issue is adding the 32bit ICD to lib32filenames else we need to go the nvidia approach and only specify the lib filename and not the full path in the .ICD file.
This issue also affects AMDVLK
next parent reply other threads:[~2019-06-16 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-3293@inbox.vuxu.org>
2019-06-16 7:16 ` voidlinux-github [this message]
2019-06-16 22:04 ` voidlinux-github
2019-06-30 16:46 ` voidlinux-github
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=20190616071659.xEYWJbN4Y6_QqD2Du0ZBIUtBmgHDwjtgFMUiOQk7oSk@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).