You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN="/home/manlio/.local/bin"
GOCACHE="/home/manlio/.cache/go-build"
GOENV="/home/manlio/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE="*.local"
GOMODCACHE="/home/manlio/.local/lib/go/pkg/mod"
GONOPROXY=""
GONOSUMDB="*.local"
GOOS="linux"
GOPATH="/home/manlio/.local/lib/go:/home/manlio/src/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.16.3"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2241291915=/tmp/go-build -gno-record-gcc-switches"
GOROOT/bin/go version: go version go1.16.3 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.16.3
uname -sr: Linux 5.11.15-arch1-2
/usr/lib/libc.so.6: GNU C Library (GNU libc) release release version 2.33.
gdb --version: GNU gdb (GDB) 10.1
What did you do?
Running go bug from the Go repository.
What did you expect to see?
To see the go version and go env from the go command i'm using.
What did you see instead?
The go version and go env from the version of go from the version of go installed on the system.
Notes
I think that it is wrong for go bug to use the relative path to the go command. I'm also not sure to understand the need to show GOROOT/bin/go. The header in the bug report clearly says "What version of Go are you using", not "What version of Go is installed on your system".
For this reason I suggest that the entry GOROOT/bin/go should be removed, and the entry GOROOT/bin/go tool compile -V should be replaced with `go tool compile -V.
Note that when using, as an example, go1.10.3 bug from go get golang.org/dl/go1.10.3, GOROOT/bin/ is set as the first entry in PATH, so there is no problem.
The text was updated successfully, but these errors were encountered:
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Running
go bug
from the Go repository.What did you expect to see?
To see the
go version
andgo env
from thego
command i'm using.What did you see instead?
The
go version
andgo env
from the version ofgo
from the version ofgo
installed on the system.Notes
I think that it is wrong for
go bug
to use the relative path to thego
command. I'm also not sure to understand the need to showGOROOT/bin/go
. The header in the bug report clearly says "What version of Go are you using", not "What version of Go is installed on your system".For this reason I suggest that the entry
GOROOT/bin/go
should be removed, and the entryGOROOT/bin/go tool compile -V
should be replaced with `go tool compile -V.Note that when using, as an example,
go1.10.3 bug
fromgo get golang.org/dl/go1.10.3
,GOROOT/bin/
is set as the first entry inPATH
, so there is no problem.The text was updated successfully, but these errors were encountered: