4 ms·
How long does a fully bootstrapped build take?
by dataflow 3y ago
How long does a fully bootstrapped build take?
- pharmakom 3y agoWith caching, just the time to download the artefact.
- dataflow 3y agoDoesn't caching completely defeat the point of bootstrapping? How do you know the cached artifact is correct? You have to build it manually to verify that, at which point you're still building manually...
- __MatrixMan__ 3y ago1. hash it 2. rebuild it without the cache 3. hash that 4. compare Or, trust somebody who has. Inconvenient, but is there any other way to establish trust in the correspondence between code and a binary?
- mbakke 3y agoGuix has tooling to verify binaries: https://guix.gnu.org/en/manual/en/html_node/Invoking-guix-challenge.html https://guix.gnu.org/en/manual/en/html_node/Invoking-guix-ch... "guix build --no-grafts --no-substitutes --check foo" will force a local rebuild of package foo and fail if the result is not bit-identical. "guix challenge" will compare your local binaries against multiple cache servers. I build everything locally and compare my results with the official substitute servers from time to time.
- pharmakom 3y agoYou have a hash that n trusted parties agree on. This is enabled by reproducible builds.
- mbakke 3y agoIt obviously depends on the hardware, but IIRC for me maybe 3-4 hours building from the 357 byte seed to the latest GCC. The early binaries are not very optimized :-)