From: ludo@gnu.org (Ludovic Courtès)
To: "Z. Ren" <zren@dlut.edu.cn>
Cc: 29646-done@debbugs.gnu.org
Subject: bug#29646: [PATCH] skalibs reproducible issue (reopen)
Date: Mon, 11 Dec 2017 17:08:35 +0100 [thread overview]
Message-ID: <87lgi9xn5o.fsf@gnu.org> (raw)
In-Reply-To: <20171210154045.GB30811@air> (Z. Ren's message of "Sun, 10 Dec 2017 23:42:30 +0800")
Hello,
"Z. Ren" <zren@dlut.edu.cn> skribis:
> Previously, we submitted a patch that intended to fix the unreproducible issue of the package skalibs (#28017). Unfortunately, the patch we submitted only partially fixed the issues, i.e,. for the .a file (lib/skalibs/libskarnet.a). However, the .so file (lib/libskarnet.so) is still non-deterministic.
>
> After investigation, we find that in the Makefile, 'sort' should be applied associated with 'wildcard', rather than with only ALL_SRCS.
>
> To validate the fix, we applied "guix build --check --no-grafts --rounds=2 skalibs" with the patched skarnet.scm, over three PCs (with guix 316fd29f9b6b0941367f54f431ef99695b16a9e5), and checked the sha256sum of the built files. Under our testing setup, the attached patch fixes the issues for the .a/.so files for skalibs. Hope the patch is correct this time, and sorry that the previous submitted patch failed to resolve all the unreproducible issues.
I confirm that it builds reproducibly on my laptop with --rounds=2 (a
weaker test that what you did!).
> From 36e35a72942a561028f93e6905cab7729a0d1f12 Mon Sep 17 00:00:00 2001
> From: Z. Ren <zren@dlut.edu.cn>
> Date: Sun, 10 Dec 2017 22:23:32 +0800
> Subject: [PATCH] fix the unreproducible issue for skalibs
>
> ---
> gnu/packages/skarnet.scm | 4 ++--
I adjusted the commit log and committed.
Thank you!
Ludo’.
prev parent reply other threads:[~2017-12-11 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-10 15:42 [bug#29646] [PATCH] skalibs reproducible issue (reopen) Z. Ren
2017-12-11 16:08 ` 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
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=87lgi9xn5o.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29646-done@debbugs.gnu.org \
--cc=zren@dlut.edu.cn \
/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).