From: ludo@gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: 20272@debbugs.gnu.org
Subject: bug#20272: Support reproducible builds
Date: Thu, 15 Dec 2016 00:32:47 +0100 [thread overview]
Message-ID: <87vaumgk80.fsf@gnu.org> (raw)
In-Reply-To: <87twa6iikd.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 14 Dec 2016 17:25:38 +0100")
ludo@gnu.org (Ludovic Courtès) skribis:
> Jan Nieuwenhuizen <janneke@gnu.org> skribis:
>
>> I have been building quite some versions of Guile the past week. There
>> re a couple of .go files that keep giving me problems wrt
>> nondeterminism:
>>
>> web/server/http.go
>>
>> (define *timer* (gettimeofday)) seemed suspect, but seems harmless.
>>
>> rnrs/arithmetic/fixnums.go
>>
>> make-implementation-restriction-violation seemed suspect, but commenting
>> it out does not seem to help.
>>
>> After commenting out all of http.scm and fixnums.scm, yesterday I had 3
>> Guix builds on two machines (GuixSD and one Ubuntu+Guix) that were
>> bit-identical, but one build showed differences in
>>
>> system/repl/commands.go
>>
>> Apparently most of the time this file builds deterministicly, but some
>> times it does not!? Ideas?
>
> Did you look at these differences with diffoscope? That would be
> useful.
I built it with ‘guix build --rounds=2 -K’ and got 17 differing .go
files. I looked at srfi/srfi-9/gnu.go with ediff + hexl-mode in Emacs
and found a dozen of “t-XYZ” and “tmp-XYZ” identifiers with a different
value for XYZ (an integer).
To be continued…
Ludo’.
next prev parent reply other threads:[~2016-12-14 23:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 11:48 bug#20272: Support reproducible builds Ludovic Courtès
2016-02-04 2:41 ` Mark H Weaver
2016-02-04 9:35 ` Ludovic Courtès
2016-06-20 15:46 ` Andy Wingo
2016-02-11 7:09 ` Mark H Weaver
2016-02-12 16:29 ` Mark H Weaver
2016-06-20 15:48 ` Andy Wingo
2016-06-23 19:22 ` Andy Wingo
2016-11-03 6:54 ` Jan Nieuwenhuizen
2016-11-14 21:44 ` Jan Nieuwenhuizen
2016-12-14 16:25 ` Ludovic Courtès
2016-12-14 23:32 ` Ludovic Courtès [this message]
2016-12-14 23:42 ` Ludovic Courtès
2016-12-20 23:00 ` Ludovic Courtès
2016-12-21 23:53 ` Ludovic Courtès
2016-12-30 21:00 ` Ludovic Courtès
2017-03-07 19:55 ` Ludovic Courtès
2017-02-28 13:26 ` Andy Wingo
2017-03-05 20:49 ` Ludovic Courtès
2017-03-06 20:13 ` Andy Wingo
2020-06-01 20:45 ` Andreas Rammhold
2020-06-02 12:25 ` Andreas Rammhold
[not found] ` <87o8lcu1v8.fsf@gmail.com>
2020-11-24 4:44 ` Vagrant Cascadian
2023-11-17 20:28 ` Bernhard M. Wiedemann
2024-04-08 17:27 ` Thompson, David
2024-04-09 4:02 ` Bernhard M. Wiedemann
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vaumgk80.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=20272@debbugs.gnu.org \
--cc=janneke@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.
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).