unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Kaelyn <kaelyn.alexi@protonmail.com>
Cc: John Kehayias <john.kehayias@protonmail.com>,
	 Andreas Enge <andreas@enge.fr>,  guix-devel <guix-devel@gnu.org>
Subject: Re: Mesa vulkan layer path fix for core-updates
Date: Wed, 10 May 2023 08:20:14 -0400	[thread overview]
Message-ID: <87sfc4qsxt.fsf@gmail.com> (raw)
In-Reply-To: <VMty2Q90jsAplzgyIH7LvCHYaxVaMEWBZcdIcEbVWoLeX1Ul00_2N9aUcmvGt4iXPnO81Z9R96CBHg7GjNDzX0smbb2b_Jdduwfs4Rcn5gU=@protonmail.com> (Kaelyn's message of "Tue, 09 May 2023 14:56:22 +0000")

Hi Kaelyn,

[...]

> Yes they can be. As a quick smoke test, prior to these patches
> landing, "vulkaninfo > /dev/null" would consistently print out vulkan
> loader errors about not being able to open
> libVkLayer_MESA_device_select.so. (I call it a smoke test because that
> layer not being found isn't fatal; I first encountered the errors in a
> breaking way when packaging vulkan-validationlayers for use with the
> tutorial at https://vulkan-tutorial.com/.)
>
> Slightly off-topic speaking of mesa bugs: another one that can be
> closed is https://issues.guix.gnu.org/43849 as the issue with mesa's
> reproducibility was fixed with a patch that landed in meson 0.59.0
> (which Guix picked up in commit b15c3dd9b0 from July 2021).

I've verified that mesa builds reproducibly now and closed 43849.

Thanks for the heads-up!

-- 
Thanks,
Maxim


      reply	other threads:[~2023-05-10 12:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 14:41 Mesa vulkan layer path fix for core-updates Kaelyn
2023-04-19 15:26 ` 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 [this message]

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=87sfc4qsxt.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=john.kehayias@protonmail.com \
    --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 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).