New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/vgo: Second vgo build execution gives an error #24069
Comments
I have the same issue in a more simple scenario, just pure
I ran a recent vgo (
but it still breaks next time we run
The version gets rewritten as a side effect of the second
|
@mmikulicic As you already pointed out I can echo that this issue also occurs for me. A minimal example to reproduce the issue has been uploaded to https://github.com/mewspring/pixel-vgo-example
Contents of
However, running
|
The original report by @franciscocpg is a duplicate of #24585. The #24069 (comment) by @mmikulicic is a duplicate of #24476. Closing this one. |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.10 linux/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?GOARCH="amd64"
GOBIN="/home/francisco/go/bin"
GOCACHE="/home/francisco/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/francisco/go"
GORACE=""
GOROOT="/usr/lib/go"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
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-build916224046=/tmp/go-build -gno-record-gcc-switches"
What did you do?
I'm trying
vgo
in a project that already usesdep
. It's a library (still not open source but will be soon).I run
CC=gcc vgo build
(See #23965 (comment)) and the process runs successfully.If I run
CC=gcc vgo build
again I get the errorI put
go.mod
,Gopkg.lock
andGopkg.toml
in this gist.What did you expect to see?
A successful build.
What did you see instead?
A failed build.
The text was updated successfully, but these errors were encountered: