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
Programs built with Go 1.10 or before use a way of issuing system calls that is no longer supported by the kernel on macOS 12 Monterey. In Go 1.11 and later, system calls are issued via libSystem.dylib, which is supported by the OS.
I installed minishift through brew. The solution above says to recompile the binaries using a golang version past 1.11. Is it just the OC part that needs to be recompiled, or the whole thing? https://github.com/openshift/origin/releases/tag/v3.11.0
Expected
Getting the right compiled version though brew.
Actual
% oc status
fatal error: runtime: bsdthread_register error
General information
Steps to reproduce
The cluster starts, but the command line stuff does not work. It looks like I'm running into the golang on Monterey issue:
https://github.com/golang/go/wiki/MacOS12BSDThreadRegisterIssue
I installed minishift through brew. The solution above says to recompile the binaries using a golang version past 1.11. Is it just the OC part that needs to be recompiled, or the whole thing? https://github.com/openshift/origin/releases/tag/v3.11.0
Expected
Getting the right compiled version though brew.
Actual
% oc status
fatal error: runtime: bsdthread_register error
runtime stack:
runtime.throw(0x37ead3b, 0x21)
/usr/local/go/src/runtime/panic.go:616 +0x81 fp=0x7ff7bfeff8f8 sp=0x7ff7bfeff8d8 pc=0x102ae91
runtime.goenvs()
/usr/local/go/src/runtime/os_darwin.go:129 +0x83 fp=0x7ff7bfeff928 sp=0x7ff7bfeff8f8 pc=0x1028a13
runtime.schedinit()
/usr/local/go/src/runtime/proc.go:501 +0xd6 fp=0x7ff7bfeff990 sp=0x7ff7bfeff928 pc=0x102d786
runtime.rt0_go(0x7ff7bfeff9c0, 0x2, 0x7ff7bfeff9c0, 0x1000000, 0x2, 0x7ff7bfeffb28, 0x7ff7bfeffb2b, 0x0, 0x7ff7bfeffb32, 0x7ff7bfeffb5a, ...)
/usr/local/go/src/runtime/asm_amd64.s:252 +0x1f4 fp=0x7ff7bfeff998 sp=0x7ff7bfeff990 pc=0x1056af4
The text was updated successfully, but these errors were encountered: