syscall.SIGUSR1,syscall.SIGUSR2,syscall.SIGTSTP,syscall.Kill makes endless unusable on windows #30
Comments
|
Windows does not provide sophisticated process controls or signalling; the best endless would be able to achieve on Windows is hard restarts. |
|
This is problematic for even developing on windows. I export to linux, but developing should not be affected. |
|
..\vendor\github.com\fvbock\endless\endless.go:64: undefined: syscall.SIGUSR1 windows 64 - bit operating system, Gogland IDEA, Go SDK1.8 。 |
|
$ CGO_ENABLED=0 GOOS=windows GOARCH=amd64 go build -o demo_win main.go |
xxx.go:64:3: undefined: syscall.SIGUSR1 xxx.go:65:3: undefined: syscall.SIGUSR2 xxx.go:68:3: undefined: syscall.SIGTSTP xxx.go:111:5: undefined: syscall.SIGUSR1 xxx.go:112:5: undefined: syscall.SIGUSR2 xxx.go:115:5: undefined: syscall.SIGTSTP xxx.go:119:5: undefined: syscall.SIGUSR1 xxx.go:120:5: undefined: syscall.SIGUSR2 xxx.go:123:5: undefined: syscall.SIGTSTP xxx.go:224:3: undefined: syscall.Kill xxx.go:224:3: too many errors after fixing, it can be compiled normally The items in question are: fvbock/endless#30
i found
endlessusessyscall.SIGUSR1,syscall.SIGUSR2,syscall.SIGTSTP,syscall.Kill, these things are not defined on Go 1.6.2 on windows. so codes usingendlesscan not even be compiled.endless: 2cdc20a
would you please fix this?
The text was updated successfully, but these errors were encountered: