| 25 May 2021 |
baloo | (on the one I tried) | 23:58:11 |
andi- | two machines with the same CPU result in the same output? | 23:58:20 |
andi- | (might be harder for us to test unless we rent some machines temprorary) | 23:58:33 |
baloo | I haven't tried | 23:58:33 |
andi- | * (might be harder for us to test unless we rent some machines temporary) | 23:58:38 |
baloo | yeah I can rent two machines I guess | 23:58:46 |
andi- | That might be something grahamc (he/him) could probably help with. Packet boxes might be really nice for this. | 23:59:15 |
baloo | yeah :D | 23:59:31 |
| 26 May 2021 |
baloo | the resource is need is time though | 00:00:07 |
baloo | I need* | 00:00:11 |
baloo | I have access to packet servers from work | 00:00:43 |
andi- | Well perhaps make a multi-multi-multi output derivation first that spits out all the phases and then we can think about running it on different machines | 00:00:46 |
andi- | or simply copy the build root into an output at the end | 00:01:16 |
baloo | additional challenge: because the intermediate stages are large, gcc optimizes it and rewrites them | 00:01:31 |
baloo | so you need to step manually, snapshot it, | 00:01:44 |
baloo | which is ... and extra hurdle | 00:01:51 |
andi- | Well perhaps a patch to the Makefiles then? | 00:02:07 |
andi- | Before each stage copy them to $debug/$stage | 00:02:16 |
baloo | :D | 00:02:15 |
baloo | NOPE | 00:02:21 |
baloo | not a solution either, not touching those makefiles | 00:02:32 |
andi- | perhaps just use clang :P | 00:02:41 |
baloo | https://github.com/gcc-mirror/gcc/blob/master/Makefile.in | 00:03:01 |
baloo | :D | 00:03:02 |
baloo | like ... there is a lot of makefile | 00:03:11 |
andi- | I touched them when I was working on my own nix based package set.. You can do that... it just isn't pretty | 00:03:23 |
andi- | baloo: > # Makefile.in is generated from Makefile.tpl by 'autogen Makefile.def'. | 00:04:10 |
andi- | So perhaps it is even easier | 00:04:19 |
baloo | ho | 00:04:20 |
baloo | yeah, could be a bit easier | 00:04:28 |