[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Preparing the reduced bootstrap tarballs, take 3

From: Jan Nieuwenhuizen
Subject: Re: Preparing the reduced bootstrap tarballs, take 3
Date: Mon, 03 Dec 2018 18:25:47 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

Ludovic Courtès writes:

Hello Ludo',

> Jan Nieuwenhuizen <address@hidden> 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:
> address@hidden ~/src/guix/+core-updates-next$ ./pre-inst-env guix build 
> bootstrap-tarballs
> /gnu/store/n8lrszv7qf0rwqhibm57d8jykj253bw2-bootstrap-tarballs-0
> address@hidden ~/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 <>, but maybe there are
> remnants around.)  I’ve uploaded mine here:
> <>
> Could you share yours so we can compare?

Mine is here 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.


Jan Nieuwenhuizen <address@hidden> | GNU LilyPond
Freelance IT | Avatar®

reply via email to

[Prev in Thread] Current Thread [Next in Thread]