cmd/go: reuses cached build affected by -ldflags and -X #18970
Labels
Comments
|
Use go install -v to check that the program is being rebuilt (or just check
the timestamps). My suspicion is the binary has not been rebuilt.
…On Tue, 7 Feb 2017, 11:11 Will Faught ***@***.***> wrote:
What version of Go are you using (go version)?
go version go1.7.5 darwin/amd64
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/will.faught/Developer/go"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.7.5/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.7.5/libexec/pkg/tool/darwin_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/jt/c0hjffqj6gxbhy00gm0btzkr79h225/T/go-build129389905=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
What did you do?
$ cd mymainpackage
$ go install -ldflags "-X github.com/foo/bar.Version=123"
$ mymainpackage --version # prints github.com/foo/bar.Version
123
$ go install -ldflags "-X github.com/foo/bar.Version=456" # 456 instead of 123
$ mymainpackage --version
What did you expect to see?
456
What did you see instead?
123
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#18970>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAcA1XoCUKSee9v6dDiWbkrqz_woIO0ks5rZ7a6gaJpZM4L4409>
.
|
|
Solving this issue essentially requires that, either:
1. cmd/go saves a copy of the all linker command line flags in the binary,
or
2. always rebuild the binary.
I think neither is satisfactory.
|
|
Duplicate of #18369. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Go are you using (
go version)?What operating system and processor architecture are you using (
go env)?What did you do?
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: