From: Jack Hill <jackhill@jackhill.us>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: guix-devel@gnu.org, "Léo Le Bouter" <lle-bout@zaclys.net>
Subject: Re: Request to verify powerpc64-linux bootstrap binaries
Date: Tue, 2 Jun 2020 10:16:05 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.20.2006021008280.5735@marsh.hcoop.net> (raw)
In-Reply-To: <58106de1-bc26-7256-292d-17abc2ce19ee@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
On Tue, 2 Jun 2020, Vincent Legoll wrote:
> Hello,
>
> On 02/06/2020 04:56, Chris Marusich wrote:
>> Hopefully, you'll get identical results! You don't have to run "guix
>> gc" if you don't want to, but doing so will increase the likelihood of
>> catching nondeterminism issues propagated from dependencies (which seem
>> unlikely, but you never know). It took 3 or 4 for me hours on a modern
>> 16-core machine.
heh, it didn't take that much longer, 530 minutes on my less modern 2-core
x86_64 machine.
>> Once we verify the binaries, we can actually start using them to build
>> stuff! Léo has already gotten an optimistic start on that work, and
>> many things are building successfully. Exciting!!
>
> Almost there...
yes, congratulations!
> 87f7583cf483ac3ba0ab978862873e68757bc4ddd10f739a90a9e4598f79e7fa45ec369c6efcff8d72fba87ea99f1e7a01a39450c7bf20790bc1d89d4b69a15b
> /gnu/store/dy4fhy2vqyxqfad59mfdqdd0qpcrwmyx-bootstrap-tarballs-0/gcc-stripped-5.5.0-powerpc64-linux-gnu.tar.xz
I can confirm the difference with gcc-stripped. Mine was
15f93200ef1cdde5a5721b1d4cfb4c9c5e22b4b945c77f56f60c388da99cf557d13474d14205a529cf9af9f29fb69591e17392387c0444e0efb7c85edcf30ff0
All the other hashes were the same.
Best,
Jack
next prev parent reply other threads:[~2020-06-02 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 2:56 Request to verify powerpc64-linux bootstrap binaries Chris Marusich
2020-06-02 8:57 ` Vincent Legoll
2020-06-02 14:16 ` Jack Hill [this message]
2020-06-02 19:09 ` Chris Marusich
2020-06-03 4:01 ` Jack Hill
2020-06-02 12:35 ` Maxim Cournoyer
2020-06-04 6:34 ` Efraim Flashner
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=alpine.DEB.2.20.2006021008280.5735@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=guix-devel@gnu.org \
--cc=lle-bout@zaclys.net \
--cc=vincent.legoll@gmail.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 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).