I found my problem was caused by an unsuccessfully exited process. Thanks for your help anyway.
在 2016年12月14日星期三 UTC+1上午1:25:48，Dave Cheney写道： > > Try go install -v, you'll find the program in $GOPATH/bin. If you get no > lines of output, then the program is up to date. > > On Wednesday, 14 December 2016 11:14:06 UTC+11, ddxgz1...@gmail.com wrote: >> >> Hi Uriel, >> >> How did you solve this problem? Because I'm facing the same. >> >> 在 2015年8月12日星期三 UTC+2上午10:29:39，Uriel Fanelli写道： >>> >>> >>> Hi all >>> >>> I am facing a strange behavior in "go build" process. >>> >>> What I am doing is , from time to time, to do a git pull from a github >>> repository and recompile the source >>> of a program. (the program is "gogs", https://github.com/gogits/gogs , >>> just for mention). >>> >>> What happens to me is that I compile an executable , and the binary is >>> always the same, regardless the source >>> code has changed. >>> >>> At the beginning I tried with all favours of "go clean", like "go clean >>> -r" , but the result is the same: after a certain moment, >>> dunno why, one machine has continued to produce an "old" binary, and it >>> was the machine I used to compile the same program in the past. >>> >>> Now, my question is: is there any kind of cache, tmp file, whatever the >>> compiler uses, which I could try to clean >>> in order to have a very new executable? This issue is making me crazy, >>> seems this machine is producing always the same >>> executable. >>> >>> The version of golang I'm using is 1.4.2 64 bit, CC=gcc48 >>> >>> Uriel >>> >>> >>> >>> -- 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.
