-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
cmd/go: windows build doesn't report write error #18014
Comments
Please use -x to confirm that the go tool is compiling something. |
OK, but shouldn't compiler inform user about such error by default? Any text editor does, for instance. And it's not displaying error message anyway. |
If there is nothing to compile, go build will do nothing.
|
Please copy & paste here the command you run (with |
go build -ldflags="-H windowsgui" -x
I've stripped c:\users\username part. |
It doesn't look like you've set GOPATH
|
It's set to c:\Data\go. And sometimes there's mv instead of cp, like "mv $WORK_\C_\Data\git\translations\go\gui\quarkChecker_obj\exe\a.out.exe quarkChecker.exe". |
It doesn't look like your source is in C:\data\go\src On Wed, 23 Nov 2016, 20:18 piotrfti notifications@github.com wrote:
|
That's true, it's in completely different location. |
Your GOPATH structure isn't optional. Go source code must reside in GOPATH\src. See Getting Started. |
Why is it obvious that test.exe was not updated? Please show a command transcript (full commands and output) with these commands in sequence:
Thanks. |
Timed out waiting for reply. |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go1.7 windows/amd64
What operating system and processor architecture are you using (
go env
)?GOARCH=amd64
GOHOSTOS=windows
GOOS=windows
GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
What did you do?
Compiled 'test.exe', run it, tried to compile to same file again while running.
What did you expect to see?
Write error.
What did you see instead?
Nothing. Go build exited without error, but 'test.exe' was obviously not updated.
The text was updated successfully, but these errors were encountered: