Addressing errors when using Endless on Windows
About 235 wordsLess than 1 minute...
Info
The content is referenced from https://learnku.com/articles/51696
Abstract
This article offers an approach to resolving errors encountered when using Endless on Windows:
*\fvbock\endless@*\endless.go:*:*: undefined: syscall.SIGUSR1
*\fvbock\endless@*\endless.go:*:*: undefined: syscall.SIGUSR2
*\fvbock\endless@*\endless.go:*:*: undefined: syscall.SIGTSTP
*\fvbock\endless@*\endless.go:*:*: undefined: syscall.Kill
Resolving
Navigate to the golang
installation directory, open the src/syscall/types_windows.go
file, and modify it by adding the following code:
// Modify `signals`, add the following code
var signals = [...]string{
// 1 - 15: ...
/** Compatibility for endless on Windows */
16: "SIGUSR1",
17: "SIGUSR2",
18: "SIGTSTP",
19: "SIGSTOP",
/** Compatibility for endless on Windows */
}
// Add the following code
/** Compatibility for endless on Windows */
func Kill(...interface{}) error {
return nil
}
const (
SIGUSR1 = Signal(16)
SIGUSR2 = Signal(17)
SIGTSTP = Signal(18)
SIGSTOP = Signal(19)
)
/** Compatibility for endless on Windows */
Powered by Waline v3.3.0