unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kaelyn <kaelyn.alexi@protonmail.com>
To: guix-devel <guix-devel@gnu.org>, Andreas Enge <andreas@enge.fr>
Cc: "59453@debbugs.gnu.org" <59453@debbugs.gnu.org>
Subject: Mesa vulkan layer path fix for core-updates
Date: Wed, 19 Apr 2023 14:41:57 +0000	[thread overview]
Message-ID: <ArXK1i9fJm7OO0by9qt0jhNDMbNi9a4O3kYlOFsto7FhGPT0Wf6xHtH977jL2-SvascRqvPIDVyf7Fo9zjM1jv69TaQZ-tS2Q96pI6b0ZVw=@protonmail.com> (raw)

Hi,

Some time back I mailed in https://issues.guix.gnu.org/59453 to fix an issue with the manifests for the vulkan layers that ship with mesa. Basically the error is that the manifests don't include the store path to the referenced libraries, only the file name. An example the error can be seen by running "vulkaninfo &| less", where this message is printed a few times:

ERROR: [Loader Message] Code 0 : libVkLayer_MESA_device_select.so: cannot open shared object file: No such file or directory


While I know it is late in the process of preparing core-updates for merging into master, I wanted to ask if it would be possible to have the patch addressed prior to the merge? I just encountered the error message again after having a need to check vulkaninfo and it reminded me of the patch. (The vulkan-validationlayers package that was recently merged to master from staging includes a similar phase for fixing the layer object path in its layer manifest.)

Thanks,
Kaelyn


             reply	other threads:[~2023-04-19 14:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 14:41 Kaelyn [this message]
2023-04-19 15:26 ` Mesa vulkan layer path fix for core-updates Andreas Enge
2023-04-19 16:07   ` Kaelyn
2023-04-19 16:38     ` John Kehayias
2023-04-25 14:15     ` Andreas Enge
2023-04-25 16:40       ` Kaelyn
2023-05-09  4:51         ` John Kehayias
2023-05-09 14:56           ` Kaelyn
2023-05-10 12:20             ` Maxim Cournoyer

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='ArXK1i9fJm7OO0by9qt0jhNDMbNi9a4O3kYlOFsto7FhGPT0Wf6xHtH977jL2-SvascRqvPIDVyf7Fo9zjM1jv69TaQZ-tS2Q96pI6b0ZVw=@protonmail.com' \
    --to=kaelyn.alexi@protonmail.com \
    --cc=59453@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --cc=guix-devel@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. 
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).