mirror of https://github.com/golang/go.git
- Build cmd with CGO_ENABLED=0. Doing so removes the C compiler toolchain from the reproducibility perimeter and also results in cmd/go and cmd/pprof binaries that are statically linked, so that they will run on a wider variety of systems. In particular the Linux versions will run on Alpine and NixOS without needing a simulation of libc.so.6. The potential downside of disabling cgo is that cmd/go and cmd/pprof use the pure Go network resolver instead of the host resolver on Unix systems. This means they will not be able to use non-DNS resolver mechanisms that may be specified in /etc/resolv.conf, such as mDNS. Neither program seems likely to need non-DNS names like those, however. macOS and Windows systems still use the host resolver, which they access without cgo. - Build cmd with -trimpath when building a release. Doing so removes $GOPATH from the file name prefixes stored in the binary, so that the build directory does not leak into the final artifacts. - When CC and CXX are empty, do not pick values to hard-code into the source tree and binaries. Instead, emit code that makes the right decision at runtime. In addition to reproducibility, this makes cross-compiled toolchains work better. A macOS toolchain cross-compiled on Linux will now correctly look for clang, instead of looking for gcc because it was built on Linux. - Convert \ to / in file names stored in .a files. These are converted to / in the final binaries, but the hashes of the .a files affect the final build ID of the binaries. Without this change, builds of a Windows toolchain on Windows and non-Windows machines produce identical binaries except for the input hash part of the build ID. - Due to the conversion of \ to / in .a files, convert back when reading inline bodies on Windows to preserve output file names in error messages. 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). For #24904. Fixes #57007. Change-Id: I665e1ef4ff207d6ff469452347dca5bfc81050e6 Reviewed-on: https://go-review.googlesource.com/c/go/+/454836 Reviewed-by: Bryan Mills <bcmills@google.com> Run-TryBot: Russ Cox <rsc@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> |
||
|---|---|---|
| .. | ||
| README | ||
| build.go | ||
| buildgo.go | ||
| buildruntime.go | ||
| buildtag.go | ||
| buildtag_test.go | ||
| buildtool.go | ||
| doc.go | ||
| exec_118.go | ||
| exec_119.go | ||
| imports.go | ||
| main.go | ||
| notgo117.go | ||
| quoted.go | ||
| sys_default.go | ||
| sys_windows.go | ||
| test.go | ||
| util.go | ||
| util_gc.go | ||
| util_gccgo.go | ||
| vfp_arm.s | ||
| vfp_default.s | ||
README
This program, dist, is the bootstrapping tool for the Go distribution. As of Go 1.5, dist and other parts of the compiler toolchain are written in Go, making bootstrapping a little more involved than in the past. The approach is to build the current release of Go with an earlier one. The process to install Go 1.x, for x ≥ 20, is: 1. Build cmd/dist with Go 1.17.13. 2. Using dist, build Go 1.x compiler toolchain with Go 1.17.13. 3. Using dist, rebuild Go 1.x compiler toolchain with itself. 4. Using dist, build Go 1.x cmd/go (as go_bootstrap) with Go 1.x compiler toolchain. 5. Using go_bootstrap, build the remaining Go 1.x standard library and commands. NOTE: During the transition from the old C-based toolchain to the Go-based one, step 2 also builds the parts of the toolchain written in C, and step 3 does not recompile those. Because of backward compatibility, although the steps above say Go 1.17.13, in practice any release ≥ Go 1.17.13 but < Go 1.x will work as the bootstrap base. See golang.org/s/go15bootstrap for more details. Compared to Go 1.4 and earlier, dist will also take over much of what used to be done by make.bash/make.bat/make.rc and all of what used to be done by run.bash/run.bat/run.rc, because it is nicer to implement that logic in Go than in three different scripting languages simultaneously.