From: maya.tomasek--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 58251@debbugs.gnu.org
Subject: bug#58251: Mesa missing patches for Vulkan shared libraries
Date: Sun, 02 Oct 2022 16:33:13 +0200 [thread overview]
Message-ID: <878rly70t2.fsf@disroot.org> (raw)
As per https://issues.guix.gnu.org/57297
> It was only recently that I was able to fix an issue with the tutorial
> program not finding the .so for the validation layer, by patching the
> layer manifest file with the full store path of the .so. A similar
> phase would need to be added to the mesa package definition for its
> device selection layer to work properly. The error from the mesa layer
> not being found when I run the basic tutorial program is:
>
> !! validation layer: libVkLayer_MESA_device_select.so: cannot open
> shared object file: No such file or directory
And the mentioned patch is:
> + #:phases #~(modify-phases %standard-phases
> + (add-after 'install 'set-layer-path-in-manifest
> + (lambda* (#:key outputs #:allow-other-keys)
> + (let* ((out (assoc-ref outputs "out"))
> + (manifest (string-append out
> + "/share/vulkan/explicit_layer.d"
> + "/VkLayer_khronos_validation.json")))
> + (substitute* manifest
> + (("\"libVkLayer_khronos_validation.so\"")
> + (string-append "\"" out
> "/lib/libVkLayer_khronos_validation.so\"")))))))))
This errors actually appears in more packages, for example vulkan-info
prints this error.
Patches to all shared vulkan libraries should be added into mesa, so
applications can actually load vulkan.
next reply other threads:[~2022-10-02 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 14:33 maya.tomasek--- via Bug reports for GNU Guix [this message]
2022-10-16 16:57 ` bug#58251: Mesa missing patches for Vulkan shared libraries Kaelyn via Bug reports for GNU Guix
2023-06-18 16:23 ` Kaelyn via Bug reports for GNU Guix
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=878rly70t2.fsf@disroot.org \
--to=bug-guix@gnu.org \
--cc=58251@debbugs.gnu.org \
--cc=maya.tomasek@disroot.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).