From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [IPv6:2a0c:4d80:42:2001::664]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id D9C6F3B29E for ; Sat, 22 Feb 2020 07:26:45 -0500 (EST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1582374404; bh=uIR6LJXcbwjfMZ1SQF1FWblvz83DauRdRo70OgoB4tQ=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=vcMgHcJUWWgssUq/YjF+rTmqyDivxML+nFn/iPYXYr+n3IHBkGXYcJ8ObI8sm36NZ 17b43Xiy/CFobei2qmiBFkGDWC0ePvXhLkF40mk0FBR7cp4xEO2wuLIWQhV94ZDp6N /4Jw0TIcnroG6WHDNZe2W7q0LmZyzNk9gRNyOYTVNm2F2dRfpJjX665PtH0M3NKeeu ui1wNAo4i0XatQeZJT7e50KJzwP1Q5kSFF8amib/Q3LwlDgdfvEH7nN49+v2mR2aHJ 0ZCDQ7WgyVxqLZSg/63qOw7CsthzNGzdmFkJXSAHzmSfPBWZi30nK0IHA75VzJmwTF LSIk+N+biQfgw== To: Rich Brown Cc: bloat@lists.bufferbloat.net In-Reply-To: <36AC0E86-7889-4A76-A253-B43A85DBD4E0@gmail.com> References: <146A9AC4-7EA6-4759-A4D1-D0613C6B650D@gmail.com> <87tv3ktcds.fsf@toke.dk> <36AC0E86-7889-4A76-A253-B43A85DBD4E0@gmail.com> Date: Sat, 22 Feb 2020 13:26:44 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87r1ymst8b.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Bloat] macOS Catalina causes 'hugo serve' to segfault... X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Feb 2020 12:26:46 -0000 Rich Brown writes: >> On Feb 21, 2020, at 6:20 AM, Toke H=C3=B8iland-J=C3=B8rgensen wrote: >>=20 >> Looking at that thread, I don't really get the feeling that they're any >> more helpful now :/ > > I can second that thought.=20 > >> As an alternative, maybe it'll be possible to build a new version of the >> 0.16 Hugo binary with a newer Go runtime? I very much doubt that the >> segfault is because of the Hugo code itself... > > My thought exactly. In case anyone has a burning urge to get > distracted on this, I'll take a whack at this over the weekend. (After > all, it's my computer that's busted...) In case anyone else wants to build the old version of Hugo, we managed to resolve this, and with a recent version of Go, the following command should now get you a working 'hugo' binary in your $GOPATH/bin: go get github.com/tohojo/hugo -Toke