3 ms·
Whilst this looses some exhotic /etc/resolv.conf compatibility it is a step towards a fully reproducable toolchain which seems a much bigger win.
by ZiiS 4y ago
Whilst this looses some exhotic /etc/resolv.conf compatibility it is a step towards a fully reproducable toolchain which seems a much bigger win.
- dgl 4y agoIt sounds like it's pretty much the final step; the toolchain will be fully reproducible on 1.21: https://go.dev/cl/454836 https://go.dev/cl/454836 The CL description describes the changes, then: "Combined, these four changes (along with Go 1.20's removal of installed pkg/*.a files and conversion of macOS net away from cgo) make the output of make.bash fully reproducible, even when cross-compiling: a released macOS toolchain built on Linux or Windows will contain exactly the same bits as a released macOS toolchain built on macOS. The word "released" in the previous sentence is important. For the build IDs in the binaries to work out the same on both systems, a VERSION file must exist to provide a consistent compiler build ID (instead of using a content hash of the binary)."