all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Kaelyn Takata <kaelyn.alexi@protonmail.com>
Cc: 49646-done@debbugs.gnu.org
Subject: bug#49646: [PATCH core-updates] gnu: meson: Update to 0.59.0.
Date: Tue, 20 Jul 2021 23:46:07 +0200	[thread overview]
Message-ID: <878s20irq8.fsf@gnu.org> (raw)
In-Reply-To: <Yq5ItF28DdgYjupEkK0mqUDKipJbY9Ifb0ASCvq88@cp7-web-039.plabs.ch> (Kaelyn Takata's message of "Mon, 19 Jul 2021 17:40:41 +0000")

Hi,

Kaelyn Takata <kaelyn.alexi@protonmail.com> skribis:

> * gnu/packages/build-tools.scm (meson): Update to 0.59.0, which includes a
> reproduceability fix for builds that link against multiple LLVM libraries.

Pushed as b15c3dd9b0e9cf6858f730e1d46c35ed9ab6a758.

> At least based on my local testing using "./pre-inst-env guix build --rounds=2 mesa", the meson upgrade fixes the reproducibility of mesa by stabilizing the link order of the LLVM libraries. I believe it will resolve the following issues:
> * https://issues.guix.gnu.org/35084 "Mesa is not reproducible (tested on staging)"
> * https://issues.guix.gnu.org/43849 "mesa is not reproducible"
> * https://issues.guix.gnu.org/48552 "mesa 20.2.4 is not reproducible"

Oh nice.  I added a “Fixes” line to the commit log.  We’ll run ‘guix
challenge’ once we have several builds of it (later on because right now
ci.guix only builds core packages on this branch and bordeaux.guix
doesn’t built it yet).

Thanks!

Ludo’.




      parent reply	other threads:[~2021-07-20 21:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 17:40 [bug#49646] [PATCH core-updates] gnu: meson: Update to 0.59.0 Kaelyn Takata via Guix-patches via
2021-07-20  6:40 ` [bug#49646] Affected mesa issues Kaelyn via Guix-patches via
2021-07-20 21:46 ` Ludovic Courtès [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878s20irq8.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=49646-done@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.