goose process constantly killed for no reason.

[Anton Shemerey]

Right after install can't do anything with it

Gettking

$ goose up
[1]    4645 killed     goose up

My go env is

GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/zork/.go"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.8/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.8/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/gv/fg1zdrz1035727qfr8w0s28h0000gn/T/go-build779470616=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"

% goose up [1] 4645 killed goose up

[Anton Shemerey]

Darwin 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar 3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64 MacOS SIerra 10.12.4

[Calvin Cheng]

I am having exactly the same issue. There seems to be a conflict with a MacOS Sierra update (10.12.4) and some go programs. go programs that get killed abruptly can be rebuilt with the -ldflags -s flag.

Example:-

    go get -u -v -ldflags -s bitbucket.org/liamstask/goose/cmd/goose

[Anton Shemerey]

Thx, Calvin this works.

[Melvin Soldia]

I second @calvinchengx 's solution works.

[Gabriel Speckhahn]

Updating to Go 1.8.1 and recompiling fixes this: https://github.com/golang/go/issues/19734