Re: Preparing the reduced bootstrap tarballs, take 3

Hi Ludovic, Ludovic Courtès writes: > Mark H Weaver skribis: > >> What commit did you use? It would be good to document this, so that >> others can independently verify our bootstrap binaries, now or in the >> future. > > The commit appears in the commit log and in this very thread, no? Yes,

Re: Preparing the reduced bootstrap tarballs, take 3

Mark H Weaver skribis: > Ludovic Courtès writes: > >> Mark H Weaver skribis: >> >>> Ludovic Courtès writes: >>> Jan Nieuwenhuizen skribis: > Ludovic Courtès writes: > > Hi! > >> I’ve just uploaded these to >>

Re: Preparing the reduced bootstrap tarballs, take 3

Ludovic Courtès writes: > Mark H Weaver skribis: > >> Ludovic Courtès writes: >> >>> Jan Nieuwenhuizen skribis: >>> Ludovic Courtès writes: Hi! > I’ve just uploaded these to > : > > linux-libre-

Re: Preparing the reduced bootstrap tarballs, take 3

Ludovic Courtès writes: >> Does our documentation include instructions on how to reproducibly build >> these new bootstrap binaries, to independently verify them? > > The build procedure remains unchanged (info "(guix) Bootstrapping"): > > guix build bootstrap-tarballs > > To verify them, you ca

Re: Preparing the reduced bootstrap tarballs, take 3

Hi Mark, Mark H Weaver skribis: > Ludovic Courtès writes: > >> Jan Nieuwenhuizen skribis: >> >>> Ludovic Courtès writes: >>> >>> Hi! >>> I’ve just uploaded these to : linux-libre-headers-stripped-4.14.67-i686-l

Re: Preparing the reduced bootstrap tarballs, take 3

Ludovic Courtès writes: > Jan Nieuwenhuizen skribis: > >> Ludovic Courtès writes: >> >> Hi! >> >>> I’ve just uploaded these to >>> : >>> >>> linux-libre-headers-stripped-4.14.67-i686-linux.tar.xz >>> linux-libre-headers-stripped-4

Re: Preparing the reduced bootstrap tarballs, take 3

Ludovic Courtès writes: > Jan Nieuwenhuizen skribis: > >> Ludovic Courtès writes: >> >> Hi! >> >>> I’ve just uploaded these to >>> : >>> >>> linux-libre-headers-stripped-4.14.67-i686-linux.tar.xz >>> linux-libre-headers-stripped-4.

Re: Preparing the reduced bootstrap tarballs, take 3

Jan Nieuwenhuizen skribis: > Ludovic Courtès writes: > > Hi! > >> I’ve just uploaded these to >> : >> >> linux-libre-headers-stripped-4.14.67-i686-linux.tar.xz >> linux-libre-headers-stripped-4.14.67-i686-linux.tar.xz.sig >> mesc

Re: Preparing the reduced bootstrap tarballs, take 3

Ludovic Courtès writes: Hi! > I’ve just uploaded these to > : > > linux-libre-headers-stripped-4.14.67-i686-linux.tar.xz > linux-libre-headers-stripped-4.14.67-i686-linux.tar.xz.sig > mescc-tools-static-0.5.2-0.bb062b0-i686-linux

Re: Preparing the reduced bootstrap tarballs, take 3

Hello! l...@gnu.org (Ludovic Courtès) skribis: > 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$ (

Re: Preparing the reduced bootstrap tarballs, take 3

Hello, Jan Nieuwenhuizen skribis: > Jan Nieuwenhuizen writes: > >>> >>> >>> >>> Could you share yours so we can compare? >> >> Mine is here >> >> >> http://lilypond.org/janneke/mes/x86_64-linux/guile-static

Re: Preparing the reduced bootstrap tarballs, take 3

Hello, Jan Nieuwenhuizen skribis: > Jan Nieuwenhuizen writes: > >>> >>> >>> >>> Could you share yours so we can compare? >> >> Mine is here >> >> >> http://lilypond.org/janneke/mes/x86_64-linux/guile-static

Re: Preparing the reduced bootstrap tarballs, take 3

Ludovic Courtès writes: Hello Ludo', > Jan Nieuwenhuizen 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

Re: Preparing the reduced bootstrap tarballs, take 3

Jan Nieuwenhuizen writes: >> >> >> >> 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

Re: Preparing the reduced bootstrap tarballs, take 3

Hello janneke, Jan Nieuwenhuizen 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. > > So, finally for core-updates-next 4ae7dc7b9af64794081b1913740b97acd89c91bc > here are my lucky n

Re: Preparing the reduced bootstrap tarballs

Hi Jan, Jan Nieuwenhuizen writes: > Timothy Sample writes: > >> I wanted to let you know that I’ve been doing more work on the little >> Shell backend that we were talking about earlier. It’s kind of like the >> worse-is-better version of Gash: it is certainly not as nice, but the >> developmen

Preparing the reduced bootstrap tarballs, take 3

Jan Nieuwenhuizen writes: Hello again! The last problem left for me before we can verify the new bootstrap tarballs and move them to ftp.gnu.org:guix was for ./pre-inst-env guix bootstrap-tarballs to succeed. We needed to force #:system "i686-linux" for mescc-tools-static and mes-minimal.

Re: Preparing the reduced bootstrap tarballs

Timothy Sample writes: Hello Timothy! >> The plan is to have Guile and Gash initially replace all coreutils&co >> and build them from source early in the bootstrap phase, right after >> having built tcc and GNU make. We have managed to build GNU make >> without any dependency on any of the tool

Preparing the reduced bootstrap tarballs, take 2

Hello! Meanwhile, I have updated core-updates-next to include d9ed0a463 bootstrap: Update %bootstrap-tarballs. 4fd4efc81 bootstrap: Replace %mescc-tools-seed with %bootstrap-mescc-tools. 562c37c7b bootstrap: Update %bootstrap-mes. b00a95be2 bootstrap: Add %bootstrap-mescc-tools.

Re: Preparing the reduced bootstrap tarballs

> Now that’s a project for a free hardware design that I’d happily work > on :) Sweet > Reading and transmitting of the bitstream can be done in hardware alone > (shift register, MUX, photoresistors, …), though I’d need to know what > kind of interface there is on the receiving side. Just flash m

Re: Preparing the reduced bootstrap tarballs

Hi Jan, Jan Nieuwenhuizen writes: > The plan is to have Guile and Gash initially replace all coreutils&co > and build them from source early in the bootstrap phase, right after > having built tcc and GNU make. We have managed to build GNU make > without any dependency on any of the tool you men

Punch cards (was Preparing the reduced bootstrap tarballs)

Hi, Ricardo Wurmus writes: > jerem...@pdp10.guru writes: > >>> for the lazyer like me, what about a punched card? :-) >> If someone is willing to figure out how to read a deck of punched cards >> without software, I'd be interested in learning more. > > Now that’s a project for a free hardware d

Re: Preparing the reduced bootstrap tarballs

jerem...@pdp10.guru writes: >> for the lazyer like me, what about a punched card? :-) > If someone is willing to figure out how to read a deck of punched cards > without software, I'd be interested in learning more. Now that’s a project for a free hardware design that I’d happily work on :) Re

Re: Preparing the reduced bootstrap tarballs

> so, if I don't get it wrong, every skilled engineer will be able to > build an "almost analogic" (zero bit of software preloaded) computing > machine ad use stage0/mes [1] as the "metre" [2] to calibrate all other > computing machines (thanks to reproducible builds)? well, I haven't thought of i

Re: Preparing the reduced bootstrap tarballs

Hi Jeremiah, jerem...@pdp10.guru writes: [...] > and once I finally complete stage0; you would also have the blueprints > for making the virtual machine in hardware, so, if I don't get it wrong, every skilled engineer will be able to build an "almost analogic" (zero bit of software preloaded) c

Re: Preparing the reduced bootstrap tarballs

Mark H Weaver writes: > Anyway, I've answered my own question by looking at: > > > https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/make-bootstrap.scm?h=core-updates-next&id=d9ed0a46301e259c3082fcc67678e72ceae19a2d#n778 > > which indicates to me that although gcc, binutils, and glib

Re: Preparing the reduced bootstrap tarballs

Hi, jerem...@pdp10.guru writes: >> However, my impression (correct me if I'm wrong) is that we are not yet >> able to bootstrap Guix exclusively from M2-Planet. > That is correct as the step of bootstrapping MesCC from M2-Planet is not > yet complete. > However once that is done, we can leverage

Re: Preparing the reduced bootstrap tarballs

> However, my impression (correct me if I'm wrong) is that we are not yet > able to bootstrap Guix exclusively from M2-Planet. That is correct as the step of bootstrapping MesCC from M2-Planet is not yet complete. However once that is done, we can leverage Mes.c and gash to complete the bootstrap o

Re: Preparing the reduced bootstrap tarballs

Jan Nieuwenhuizen writes: >> If you want, before pushing this patch, you can first push the one >> above. From there I (and possibly others!) will run “guix build >> bootstrap-tarballs” and make sure we get the same result as you did. > > Great, done. I missed > > 5b01b6034aeab32a5011c5757f1

Re: Preparing the reduced bootstrap tarballs

Ludovic Courtès writes: Hi! >> Still I hope these won't last for five more years ;-) > > Well I hope these will last for at least a couple of years, or at least > this is what we should aim for. Yes, we should aim for that while creating them. I'm possibly a bit too eager to replace the reduced

Re: Preparing the reduced bootstrap tarballs

Hi Jeremiah, jerem...@pdp10.guru writes: >> I think it's important that the new bootstrap-tarballs be >> bit-reproducible, such that they can be independently verified by anyone >> who wishes to do so. > > Every Piece below M2-Planet has always been bit-reproducible. > In fact, each piece is desi

Re: Preparing the reduced bootstrap tarballs

> I think it's important that the new bootstrap-tarballs be > bit-reproducible, such that they can be independently verified by anyone > who wishes to do so. Every Piece below M2-Planet has always been bit-reproducible. In fact, each piece is designed in a way that you could by hand predict what t

Re: Preparing the reduced bootstrap tarballs

Hello, Jan Nieuwenhuizen skribis: >> IMO we should change the seeds as rarely as possible because they are >> managed “out-of-band” and verifying them is difficult (you need to fetch >> the right Guix commit, run “guix build bootstrap-tarballs”, and compare >> the result—assuming this is all bit

Re: Preparing the reduced bootstrap tarballs

l...@gnu.org (Ludovic Courtès) writes: > jerem...@pdp10.guru skribis: > >>> So if you like, please make that change. There is only one little >>> thing: I have no (scripted) recipe to create mescc-tools-seed-XYZ. But >>> wait: I have a great excuse for that...I was too lazy or too sloppy. >> >>

Re: Preparing the reduced bootstrap tarballs

Ludovic Courtès writes: >> Ah right. I saw that several times but did not use it. I think because >> initially it was of no use. It would be nice if this built everything >> we need, I agree :-) > > Heheh. :-) It’s what the “Building the Bootstrap Binaries” section > describes. Right...and I

Re: Preparing the reduced bootstrap tarballs

Ludovic Courtès writes: > jerem...@pdp10.guru skribis: > >>> So if you like, please make that change. There is only one little >>> thing: I have no (scripted) recipe to create mescc-tools-seed-XYZ. But >>> wait: I have a great excuse for that...I was too lazy or too sloppy. >> >> I do, in mescc-

Re: Preparing the reduced bootstrap tarballs

jerem...@pdp10.guru skribis: >> So if you like, please make that change. There is only one little >> thing: I have no (scripted) recipe to create mescc-tools-seed-XYZ. But >> wait: I have a great excuse for that...I was too lazy or too sloppy. > > I do, in mescc-tools-seed; the script bootstrap.

Re: Preparing the reduced bootstrap tarballs

Hello! Jan Nieuwenhuizen skribis: > Ludovic Courtès writes: > > Hi! > >> (This is a followup to .) > >> I (finally!) run “guix build bootstrap-tarballs” on ‘core-updates-next’, >> but that was a bit silly of me since that built the x86_64-linux >> tarballs—i.e., not t

Re: Preparing the reduced bootstrap tarballs

> Indeed. "mes-seed" and "tinycc-seed" are remnants of the past; the only > things we need are > >> What we would need here is something to build the things listed in >> ‘%bootstrap-inputs’, namely: >> ‘linux-libre-headers-stripped-4.14.26-i686-linux.tar.xz’ (easy :-)), >> ‘mescc-tools-seed-XYZ

Re: Preparing the reduced bootstrap tarballs

Ludovic Courtès writes: Hi! > (This is a followup to .) > I (finally!) run “guix build bootstrap-tarballs” on ‘core-updates-next’, > but that was a bit silly of me since that built the x86_64-linux > tarballs—i.e., not the “reduced seed.” > > So I was about to re-run

Preparing the reduced bootstrap tarballs

Hello! (This is a followup to .) Jan Nieuwenhuizen skribis: > Did those, pushed to core-updates-next as > > d0bb7ed61ed9e356c53de1a8e9bd6c2ec030ffb6 > doc: Update Preparing to Use the Bootstrap Binaries. [...] > I think that I'm "done" here, there's the `pu