fail early if we know we lack Go linker patches
Right now, we only have linker patches for Go 1.22.x. We only ever maintain those for one or two major Go versions at a time. If a user tries to use the Go toolchain from 1.21, we already fail with "Go version too old" messages early on, but we don't for 1.23, causing a relatively confusing error later on when we link a binary: cannot get modified linker: cannot retrieve linker patches: open patches/go1.23: file does not exist Instead, fail early and with a good error message.pull/838/head
parent
d138afaf32
commit
9a2ef369b2
Loading…
Reference in New Issue