From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Preparing the reduced bootstrap tarballs, take 3
Date: Mon, 03 Dec 2018 18:25:47 +0100 [thread overview]
Message-ID: <875zwa34kk.fsf@gnu.org> (raw)
In-Reply-To: <87tvjvatt1.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 03 Dec 2018 09:38:50 +0100")
Ludovic Courtès writes:
Hello Ludo',
> Jan Nieuwenhuizen <janneke@gnu.org> skribis:
>
>> I have updated core-updates-next with this fix, a documentation update
>> and to also include Marius' mes bootstrap cleanups from his wip-gcc7
>> branch.
>>
>> $ for i in $(./pre-inst-env guix build bootstrap-tarballs)/*; do echo $i;guix hash $i; done
>> /gnu/store/n8lrszv7qf0rwqhibm57d8jykj253bw2-bootstrap-tarballs-0/guile-static-stripped-2.2.4-x86_64-linux.tar.xz
>> 1285hlbfahp414hy3jjdghxjfgi94aj7y3fw0pz7z27421b7z2f9
>> /gnu/store/n8lrszv7qf0rwqhibm57d8jykj253bw2-bootstrap-tarballs-0/linux-libre-headers-stripped-4.14.67-x86_64-linux.tar.xz
> So, on x86_64-linux, here’s what I got:
>
> ludo@ribbon ~/src/guix/+core-updates-next$ ./pre-inst-env guix build bootstrap-tarballs
> /gnu/store/n8lrszv7qf0rwqhibm57d8jykj253bw2-bootstrap-tarballs-0
> ludo@ribbon ~/src/guix/+core-updates-next$ (cd /gnu/store/n8lrszv7qf0rwqhibm57d8jykj253bw2-bootstrap-tarballs-0; for i in * ; do echo $i && guix hash $i ; done )
> guile-static-stripped-2.2.4-x86_64-linux.tar.xz
> 06ygv0b3dpvy93jji5yl4hdz17w4hiqm64m7ypf6g2vi4nfn9xl9
> So only ‘guile-static-stripped’ differs from yours.
Ah, beautiful!
> This may be due to
> non-determinism in bindings introduced by psyntax (something we
> addressed with <https://bugs.gnu.org/20272>, but maybe there are
> remnants around.) I’ve uploaded mine here:
>
> <http://web.fdn.fr/~lcourtes/tmp/guile-static-stripped-2.2.4-x86_64-linux.tar.xz>
>
> Could you share yours so we can compare?
Mine is here
http://lilypond.org/janneke/mes/x86_64-linux/guile-static-stripped-2.2.4-x86_64-linux.tar.xz
...so it looks like we're walking a pretty big round , for --rounds=2 ;-)
> Anyway, I’ll run the “-s i686-linux” build because right now I only have
> the 64-bit ‘guile-static-stripped’, which is not what we want, silly me…
Oh! Eh, is that right? I wasn't aware...
> Should we force #:system for this one as well?
We could but then should make sure that any go files in x86_64-linux
bootstrap binaries (mes, and in time gash) are i686-linux too.
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2018-12-03 17:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 20:39 Preparing the reduced bootstrap tarballs Jeremiah
2018-11-16 18:27 ` Ludovic Courtès
2018-11-16 20:44 ` Jan Nieuwenhuizen
2018-11-17 14:05 ` Ludovic Courtès
2018-11-18 7:32 ` Jan Nieuwenhuizen
2018-11-18 10:02 ` Jan Nieuwenhuizen
2018-11-21 15:20 ` Preparing the reduced bootstrap tarballs, take 2 Jan Nieuwenhuizen
2018-11-24 7:36 ` Preparing the reduced bootstrap tarballs, take 3 Jan Nieuwenhuizen
2018-12-03 8:38 ` Ludovic Courtès
2018-12-03 17:25 ` Jan Nieuwenhuizen [this message]
2018-12-03 17:44 ` Jan Nieuwenhuizen
2018-12-09 14:07 ` Ludovic Courtès
2018-12-09 14:07 ` Ludovic Courtès
2018-12-09 14:21 ` Ludovic Courtès
2018-12-09 18:10 ` Jan Nieuwenhuizen
2018-12-11 17:36 ` Ludovic Courtès
2018-12-12 7:30 ` Jan Nieuwenhuizen
2018-12-12 23:31 ` Mark H Weaver
2018-12-14 10:51 ` Ludovic Courtès
2018-12-14 11:48 ` Jan Nieuwenhuizen
2018-12-14 21:13 ` Mark H Weaver
2018-12-15 18:12 ` Ludovic Courtès
2018-12-16 8:54 ` Mark H Weaver
2018-11-17 3:49 ` Preparing the reduced bootstrap tarballs Mark H Weaver
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=875zwa34kk.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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.