Got it, have added updated diff.

aisha

Index: Makefile
===================================================================
RCS file: /cvs/ports/net/wireguard-go/Makefile,v
retrieving revision 1.13
diff -u -p -r1.13 Makefile
--- Makefile    30 Mar 2020 14:33:11 -0000      1.13
+++ Makefile    17 Apr 2020 18:42:22 -0000
@@ -1,7 +1,5 @@
 # $OpenBSD: Makefile,v 1.13 2020/03/30 14:33:11 jasper Exp $
 
-ONLY_FOR_ARCHS = amd64
-
 COMMENT =      implementation of WireGuard in Go
 
 DISTNAME =     wireguard-go-0.0.20200320




On 4/17/20 12:53 PM, Stuart Henderson wrote:
> On 2020/04/17 11:34, Aisha Tammy wrote:
>> Upstream seems to have fixed the bug mentioned in the 1.4 change
>> which removed aarch64 and i386, but I've only tested on aarch64
>> so I've added that to the Makefile.
>>
>> I've been using this on Pine A64 LTS model for the past few weeks
>> and have not encountered any error so it is safe to add aarch64.
>>
>> comments? OK?
>>
>> aisha
>>
>> Index: Makefile
>> ===================================================================
>> RCS file: /cvs/ports/net/wireguard-go/Makefile,v
>> retrieving revision 1.13
>> diff -u -p -r1.13 Makefile
>> --- Makefile 30 Mar 2020 14:33:11 -0000      1.13
>> +++ Makefile 17 Apr 2020 15:21:58 -0000
>> @@ -1,6 +1,6 @@
>>  # $OpenBSD: Makefile,v 1.13 2020/03/30 14:33:11 jasper Exp $
>>  
>> -ONLY_FOR_ARCHS = amd64
>> +ONLY_FOR_ARCHS = amd64 aarch64
>>  
>>  COMMENT =   implementation of WireGuard in Go
>>  
>>
> 
> Better to remove ONLY_FOR_ARCHS completely, we can readd it if there's
> still a problem with i386 or (32 bit) arm.
> 
> It is more that they were using old vendored libraries rather than a bug
> as such. Which is sadly the norm with the annoying new languages.
> 

Reply via email to