all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Igor Goryachev via Guix-patches via <guix-patches@gnu.org>
To: 71899@debbugs.gnu.org
Cc: Igor Goryachev <igor@goryachev.org>, Andrew Tropin <andrew@trop.in>
Subject: [bug#71899] [PATCH v2] gnu: erlang-lfe: Make LFE compiler deterministic.
Date: Tue,  2 Jul 2024 15:46:15 +0300	[thread overview]
Message-ID: <8a8d2696560e1dfb51d106a1c5e7c9034a5e5c39.1719924375.git.igor@goryachev.org> (raw)

* gnu/packages/erlang.scm (erlang-lfe): Make LFE compiler deterministic.

Change-Id: I0cf00eeda8502384b746795802f1b2291d0e8a3b
---
 gnu/packages/erlang.scm | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/gnu/packages/erlang.scm b/gnu/packages/erlang.scm
index dd07c1a617..a236722474 100644
--- a/gnu/packages/erlang.scm
+++ b/gnu/packages/erlang.scm
@@ -792,6 +792,13 @@ (define-public erlang-lfe
       #:phases
       #~(modify-phases %standard-phases
           (delete 'configure)
+          ;; By default LFE compiler itself is not deterministic. We fix it
+          ;; here. For more details see: https://github.com/lfe/lfe/issues/492.
+          (add-after 'unpack 'make-deterministic
+           (lambda _
+             (substitute* "src/lfe_env.erl"
+                 (("maps:fold\\(F, A, D\\)")
+                  "lists:sort(maps:fold(F, A, D))"))))
           ;; The following is inspired by rebar-build-system.scm
           (add-before 'check 'erlang-depends
             (lambda* (#:key inputs #:allow-other-keys)

base-commit: 4b3a553ca5ba5ac190739309eb5f7aa8170cf2a8
-- 
2.45.2





             reply	other threads:[~2024-07-02 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02 12:46 Igor Goryachev via Guix-patches via [this message]
2024-07-03  3:30 ` bug#71899: [PATCH v2] gnu: erlang-lfe: Make LFE compiler deterministic Andrew Tropin 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=8a8d2696560e1dfb51d106a1c5e7c9034a5e5c39.1719924375.git.igor@goryachev.org \
    --to=guix-patches@gnu.org \
    --cc=71899@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=igor@goryachev.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 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.