On Mon, Feb 12, 2018 at 7:44 PM, Matt R. <matthew5...@gmail.com> wrote: > > I have a simple way to reproduce this with GOROOT defined for each golang > version. > > Install gb. https://getgb.io/ > Create a project with the structure: > > src > > app > > main.go (fill with contents of runtime example from documentation > https://golang.org/pkg/runtime/#example_Frames) > > Download a fresh copy of go 1.9.2 and 1.9.4 > Compare these builds: > > GOROOT=/path/to/go1.9.2 CGO_ENABLED=0 GOOS=freebsd GOARCH=amd64 gb build > > Works! > > GOROOT=/path/to/go1.9.4 CGO_ENABLED=0 GOOS=freebsd GOARCH=amd64 gb build > > Fails!
The error is new with Go 1.9.4, so that aspect is not surprising. It's part of the security fixes that triggered the 1.9.4 release. Can you recreate the problem *without* setting GOROOT in the environment? The most likely cause is a mismatch between GOROOT in the environment and the GOROOT used by the go program on your PATH. Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
