From owner-freebsd-arm@freebsd.org Tue Dec 31 15:13:43 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1C9161D6FCF for ; Tue, 31 Dec 2019 15:13:43 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47nHr671x4z4N5X; Tue, 31 Dec 2019 15:13:42 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1imJDG-00031l-Si; Tue, 31 Dec 2019 16:13:40 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: =?utf-8?Q?Mika=C3=ABl_Urankar?= , =?utf-8?Q?Bernhard_Fr=C3=B6hlich?= Cc: "freebsd-arm@freebsd.org" Subject: Re: is wireguard available on arm64 References: <6C673FA9-57F5-4291-A32A-7D6F9837CB74@libassi.se> Date: Tue, 31 Dec 2019 16:13:43 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/1.0 (Win32) X-Authenticated-As-Hash: bdb49c4ff80bd276e321aade33e76e02752072e2 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.2 X-Scan-Signature: 22b714be0c51703cd3047a81d17f7b3c X-Rspamd-Queue-Id: 47nHr671x4z4N5X X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; REPLY(-4.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Dec 2019 15:13:43 -0000 On Tue, 31 Dec 2019 13:54:35 +0100, Bernhard Fr=C3=B6hlich = wrote: > On Tuesday, December 31, 2019, Mika=C3=ABl Urankar > wrote: >> Le lun. 30 d=C3=A9c. 2019 =C3=A0 22:12, Peter Libassi a =C3=A9crit : >>> >>> I=E2=80=99m s newbie on BSD. Just installed freebsd on a RPI3 using = the image > https://download.freebsd.org/ftp/releases/arm64/aarch64/ISO-IMAGES/12.= 1/FreeBSD-12.1-RELEASE-arm64-aarch64-RPI3.img.xz >>> >>> which gave me release: >>> >>> FreeBSD bsd1 12.1-RELEASE FreeBSD 12.1-RELEASE r354233 GENERIC arm6= 4 >>> >>> pkg install wireguard gives message: >>> >>> Updating FreeBSD repository catalogue... >>> FreeBSD repository is up to date. >>> All repositories are up to date. >>> pkg: No packages available to install matching 'wireguard' have been= > found in the repositories >>> >>> >>> on the Port web site i find: wireguard-1.0.20191226 >>> >>> what am i doing wrong? >> >> Nothing :) >> >> go for arm64 is available as lang/go-devel. You'll need to compile it= >> manually as we only provide packages for the quarterly branch on >> RELEASE version of FreeBSD (and go-devel hasn't landed in the >> quarterly branch > > go-devel is already able to compile on arm64 and some go ports have be= en > patched for arm64 to build fine - including wireguard-go. > > So once the next quarterly branch is created (in less than 24h) and th= e > builders have finished (in a few days) we should have Go ports availab= e = > on > arm64 including wireguard. Mmmm "in a few days" is not so true. It takes about 5-7 days to build al= l = packages for one FreeBSD version on ARM64. So it takes about 2-3 weeks t= o = do a full build for head, 12.x and 11.x. You are unlucky if your version= = builds last. :-) Last full build for head: http://thunderx1.nyi.freebsd.org/build.html?mastername=3Dhead-arm64-defa= ult&build=3Dp519639_s355573 All current arm64 builds: http://thunderx1.nyi.freebsd.org/ Regards, Ronald. > > In addition to that there is a Rust based wireguard userspace > implementation in the works which should also work on FreeBSD - but th= at = > is > something for 2020.