You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On FreeBSD 12-STABLE with kernel built only with COMPAT_FREEBSD11 as required by wiki [1]:
...
ok regexp/syntax 1.706s
--- FAIL: TestSignalM (0.00s)
crash_unix_test.go:325: function not implemented
--- FAIL: TestSetNonblock (0.00s)
nbpipe_test.go:75: function not implemented
FAIL
FAIL runtime 103.442s
pipe() became a wrapper around pipe2() in FreeBSD 11.0, and on FreeBSD 11 and 12 it requires a kernel built with COMPAT_FREEBSD10 [2]. It seems that either:
wiki page [1] needs to be updated to mention that COMPAT_FREEBSD10 is required in addition to COMPAT_FREEBSD11, or
given that FreeBSD 10 is EOL, runtime·pipe needs to be rewritten to be a wrapper around runtime·pipe2, similar to [3]
Given that the final supported version for FreeBSD 10 is Go 1.12.4, FreeBSD 10 is EOL and the pipe2 syscall is available since FreeBSD 10.0 (according to https://www.freebsd.org/cgi/man.cgi?pipe(2)#IMPLEMENTATION_NOTES) let's implement runtime.pipe using the pipe2 syscall. This is already done for various other ports.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
$ ./all.bash
What did you expect to see?
All tests passing.
What did you see instead?
On FreeBSD 12-STABLE with kernel built only with COMPAT_FREEBSD11 as required by wiki [1]:
pipe()
became a wrapper aroundpipe2()
in FreeBSD 11.0, and on FreeBSD 11 and 12 it requires a kernel built with COMPAT_FREEBSD10 [2]. It seems that either:runtime·pipe
needs to be rewritten to be a wrapper aroundruntime·pipe2
, similar to [3][1] https://github.com/golang/go/wiki/FreeBSD
[2] freebsd/freebsd-src@e4ef214
[3] https://github.com/golang/go/blob/master/src/runtime/sys_freebsd_arm64.s#L131
The text was updated successfully, but these errors were encountered: