unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: 22304@debbugs.gnu.org
Subject: bug#22304: Build for Julia is not reproducible
Date: Mon, 4 Jan 2016 17:28:42 +0100	[thread overview]
Message-ID: <idj1t9xia11.fsf@bimsb-sys02.mdc-berlin.net> (raw)

When building “julia” twice we get different binaries for

  $out/lib/julia/sys.so

and

  $out/lib/julia/sys-debug.so

I could not determine the exact differences, because instead of a diff I
just see something like this:

--- /gnu/store/6njfyp46b22b0wb0r0ccg2wdzjx7066g-julia-0.4.2/lib/julia/sys.so
+++ 6njfyp46b22b0wb0r0ccg2wdzjx7066g-julia-0.4.2/lib/julia/sys.so
├── objdump --disassemble --full-contents {}
│ @@ -99994,8 +99994,8 @@
│   186a00 05a3d38a 01488985 38ffffff 488b0515  .....H..8...H...
│   186a10 5b8b0148 898540ff ffff4c89 ad48ffff  [..H..@...L..H..
│   186a20 ff31ffba 03000000 4c8db538 ffffff4c  .1......L..8...L
│   186a30 89f64989 f4e8b653 f0ff4889 8538ffff  ..I....S..H..8..
│   186a40 ff31ffba 03000000 488d9d28 ffffff49  .1......H..(...I
│   186a50 89de4c89 f6e89653 f0ff4889 8528ffff  ..L....S..H..(..
│   186a60 ff488b05 38d08a01 48898530 ffffff48  .H..8...H..0...H
│ -[ Too much input for diff ]                     
│ +[ Too much input for diff ]                         

...

--- /gnu/store/6njfyp46b22b0wb0r0ccg2wdzjx7066g-julia-0.4.2/lib/julia/sys-debug.so
+++ 6njfyp46b22b0wb0r0ccg2wdzjx7066g-julia-0.4.2/lib/julia/sys-debug.so
├── objdump --disassemble --full-contents {}
│ @@ -99994,8 +99994,8 @@
│   1869f0 01488b38 be370200 00e84257 f0ffe89d  .H.8.7....BW....
│   186a00 56f0ff66 6666662e 0f1f8400 00000000  V..ffff.........
│   186a10 554889e5 488b3e48 8b7608e8 e0fdffff  UH..H.>H.v......
│   186a20 4889c7e8 2856f0ff 5dc3660f 1f440000  H...(V..].f..D..
│   186a30 554889e5 4883ec10 64488b04 25280000  UH..H...dH..%(..
│   186a40 00488945 f848833d fb4d8d01 00740948  .H.E.H.=.M...t.H
│   186a50 8b0df24d 8d01eb1f 488d3591 ac190048  ...M....H.5....H
│ -[ Too much input for diff ]                     
│ +[ Too much input for diff ]                         
╵

~~ Ricardo

             reply	other threads:[~2016-01-04 16:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87y2pqwtyz.fsf@guixSD.i-did-not-set--mail-host-address--so-tickle-me>
2016-01-04 16:28 ` Ricardo Wurmus [this message]
2016-01-05 22:30   ` bug#22304: Build for Julia is not reproducible Ludovic Courtès
2016-02-04 14:51     ` Ricardo Wurmus
2019-11-28 17:14   ` bug#22304: Julia " zimoun
2019-11-29 16:19     ` Ludovic Courtès
2019-12-02 17:28       ` zimoun
2020-01-24 18:30         ` zimoun
2021-06-27 10:40     ` bug#22304: Build for Julia is " Ludovic Courtès
2020-05-17 13:55   ` bug#22304: [Nicolò Balzarotti] Re: Julia v1.4.1 still " Nicolò Balzarotti
2023-11-01  9:39   ` bug#22304: Julia Christopher Baines

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=idj1t9xia11.fsf@bimsb-sys02.mdc-berlin.net \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=22304@debbugs.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.
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).