all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kaelyn via Guix-patches via <guix-patches@gnu.org>
To: "58887@debbugs.gnu.org" <58887@debbugs.gnu.org>
Subject: [bug#58887] [PATCH][staging] gnu: vulkan-loader: Add native-search-paths field.
Date: Sun, 18 Jun 2023 16:31:25 +0000	[thread overview]
Message-ID: <OV4xuhjolEj41ZhXkwwdeNKQId3R1AMnwO3uys6GLuXkEaZecvr2ccOD6e5oRrXtVqFmuQrV-XcnFCDhUPr0uT_YjdpqiNyDJ6DJVtjxeOw=@protonmail.com> (raw)
In-Reply-To: <y765yg1hnql.wl-hako@ultrarare.space>

While the original patch description doesn't mention why the native-search-paths variables and associated snippet are needed, if they are to fix error messages like:


  !! validation layer: libVkLayer_MESA_device_select.so: cannot open shared object file: No such file or directory

when running Vulkan programs including vulkaninfo, then this issue can be closed. Commit 61a326442442f9b09911d35b3a3a48cf5335d7d7 fixed the remaining Vulkan layer manifest files to include the full paths to the shared libraries, which resolved the error messages like the one above about not finding the shared object files for layers without introducing new environment variables.




  parent reply	other threads:[~2023-06-18 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30  5:41 [bug#58887] [PATCH][staging] gnu: vulkan-loader: Add native-search-paths field Hilton Chain via Guix-patches via
2022-12-01 15:49 ` Ludovic Courtès
2022-12-23  7:53   ` Hilton Chain via Guix-patches via
2023-06-18 16:31 ` Kaelyn via Guix-patches via [this message]
2023-06-19  6:14   ` bug#58887: " Hilton Chain via Guix-patches via

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='OV4xuhjolEj41ZhXkwwdeNKQId3R1AMnwO3uys6GLuXkEaZecvr2ccOD6e5oRrXtVqFmuQrV-XcnFCDhUPr0uT_YjdpqiNyDJ6DJVtjxeOw=@protonmail.com' \
    --to=guix-patches@gnu.org \
    --cc=58887@debbugs.gnu.org \
    --cc=kaelyn.alexi@protonmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.