| 26 May 2021 |
 Gytis Ivaskevicius | it all depends on trust policy that our supreme Nix overlords wish to enforce. Both options make sense but If i'd had to choose - i'd rather never update bootstrap tools | 09:45:57 |
 andi- | For a trust perspective that is the ultimate goal. I already expressed that in the rustc bootstrap thread. I'd rather bootstrap via mrustc + 5 newer releases of rustc than always updating the binaries that we pull from "random places". It is worse there as we aren't even building our own boostrap tools. | 09:47:29 |
| andi- | For the GCC world we at least routinely exercise creating the bootstrap files and can show a trail for how they came to be. | 09:47:54 |
| Gytis Ivaskevicius | In reply to @andi:kack.it
For a trust perspective that is the ultimate goal. I already expressed that in the rustc bootstrap thread. I'd rather bootstrap via mrustc + 5 newer releases of rustc than always updating the binaries that we pull from "random places". It is worse there as we aren't even building our own boostrap tools. Oh, i noticed this too. Havent checked for the thread tho. Imma go search for it :D | 09:48:17 |
| andi- | I think it is dead now.. Last activity about a year or so ago. | 09:48:34 |
| Gytis Ivaskevicius | Good old "it is still important" comment will change the activity date :D | 09:49:05 |
| Gytis Ivaskevicius | Also about rustc - i heard that there are plans to get gcc to compile rust due to linux kernel - that would open few doors 👀 | 09:50:10 |
| Gytis Ivaskevicius | https://github.com/NixOS/nixpkgs/issues/72606 | 09:51:28 |
 Jonas Chevalier | same with Go. We used to bootstrap from 5 versions but switched back to binary bootrstrap | 09:51:29 |
| Gytis Ivaskevicius | what, why? | 09:53:20 |
| Gytis Ivaskevicius | I thought gcc can compile Go 🤔 | 09:53:32 |
| andi- | IIRC only until Go 1.6 | 09:55:02 |
| Gytis Ivaskevicius | ahh | 09:55:16 |
| andi- | and perhaps the bootstrap was getting too slow for some.. | 09:55:18 |
| andi- | and wasn't GccGO being removed in GCC9 or something? | 09:55:30 |
| Gytis Ivaskevicius | https://golang.org/doc/install/gccgo | 09:56:04 |
| andi- | ah nice so we got at last Go 1.12.1 | 10:00:12 |
| andi- | * ah nice so we got at last Go 1.12.2 | 10:00:16 |
| andi- | * ah nice so we got at least Go 1.12.2 | 10:00:22 |
| andi- | Given how fast Go usually compiles that should be a bootstrap that is done in less than 30min? | 10:00:48 |
| Gytis Ivaskevicius | I have not looked into dependencies of go, but it should not take long | 10:01:19 |
| andi- | My assumption was that all the deps are statitified. Purely the Go -> Go' -> Go'' -> Go''' ... dance | 10:02:19 |
| Gytis Ivaskevicius | I was helping out Dram fixing his super minimal gcc derivation https://github.com/dramforever/scratchix/blob/main/pkgs/stage1/gcc.nix - for me it compiles under 2min (tho i got a powerful pc) | 10:02:20 |
| andi- | IMHO it is fair to assume that hydra builders have 16 threads in 2021... If it takes one of those boxes less than a few hours to do the full bootstrap it should be fine. On my dated 2020 workstation I can build bootstrap -> Qemu in about 10 minutes. | 10:03:33 |
| andi- | Or was it 15? Anyway, reasonably fast for debugging.. not fun for watching | 10:04:03 |
| Gytis Ivaskevicius | i thought they bought 64 core monster at some point 🤔 | 10:04:15 |
| Gytis Ivaskevicius | might be confusing it with something | 10:04:21 |
| andi- | The hydra build farm is a mixture that is mostly made up of Packet.net computers but there are some older "on-premise" beasts. | 10:04:49 |
| Gytis Ivaskevicius | Ah, in that case i probably just saw someones htop, maybe zimbat? not sure | 10:08:04 |
| Gytis Ivaskevicius | it was a while back | 10:08:10 |
