Date: Tue, 31 Dec 2019 09:13:24 +0000 From: "Dave Cottlehuber" <dch@skunkwerks.at> To: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: is wireguard available on arm64 Message-ID: <d07f0976-1f7f-4d8d-9f01-306dca478c7e@www.fastmail.com> In-Reply-To: <FB71632C-F4BA-406F-AE69-3236D4EEF9B2@gromit.dlib.vt.edu> References: <6C673FA9-57F5-4291-A32A-7D6F9837CB74@libassi.se> <FB71632C-F4BA-406F-AE69-3236D4EEF9B2@gromit.dlib.vt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 30 Dec 2019, at 22:17, Paul Mather wrote: > > You're not doing anything wrong. According to my quick look on > freshports.org for the net/wireguard package, it shows a runtime > dependency on net/wireguard-go, and I don't believe Go currently works > on FreeBSD/arm64 (though folks on here have said it can be built if you > do a native build on an actual FreeBSD/arm64 itself---not a QEMU > cross-build). > > There was a thread about building Go and Go-based ports here on > freebsd-arm not so long ago. I got the sense from that thread that the > situation was improving wrt. Go working on FreeBSD/arm64. Looks like it will land in Go 1.14. There's a go 1.14 beta maybe you can use this to generate an arm64 binary from another system? I'm not sure if FreeBSD can directly build go 1.14 from source on arm64 yet. Let us know ;-) - https://github.com/golang/go/issues/24715 - https://github.com/golang/go/commit/eeb319a5 A+ Dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d07f0976-1f7f-4d8d-9f01-306dca478c7e>