On 2024/07/07 21:09, Kian Ali Agheli wrote:
>
> OpenBSD recently changed access to its syscalls.
> The change which allows upstream Go to build working executables
> for current OpenBSD was committed on May 4th.
> https://github.com/golang/go/commit/8841f50d98b224ecf5ee27d9b7e6f18ad2c98e46
That i
On 2024/07/07 22:06, Chris Narkiewicz wrote:
> There is plenty of go applications in ports, so I guess this
> is a solved problem.
Not completely - some of these still try to use syscall and fail at
runtime.
- Forwarded message from Kian Ali Agheli -
Date: Sun, 7 Jul 2024 21:08:11 -0700
From: Kian Ali Agheli
To: Qingyao Sun
Subject: Re: Pre-compiled static go binary fails with "undefined symbol
'syscall'"
OpenBSD recently changed access to its syscalls.
The
On Sun, Jul 07, 2024 at 04:58:47PM -0400, Qingyao Sun wrote:
> > Then that would be a bug in Go's stdlib on OpenBSD. Sadly I know
> nothing
> > about OpenBSD, so I cant help you with that. From the error message
> > OpenBSD's libc is apparently missing syscall.
Yes, syscall has
