From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from neet.inri.net ([107.191.102.52]) by ur; Wed Nov 23 10:57:28 EST 2016 Received: (qmail 52038 invoked from network); 23 Nov 2016 15:56:46 -0000 Received: from mobile-166-175-189-25.mycingular.net (HELO ?10.205.66.161?) (sl@166.175.189.25) by neet.inri.net with SMTP; 23 Nov 2016 15:56:46 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: [9front] easy install of go on 9front? From: Stanley Lieber X-Mailer: iPhone Mail (14B100) In-Reply-To: Date: Wed, 23 Nov 2016 10:57:27 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <791A1F3F-85EE-4108-9DDB-8AA3689C35E9@stanleylieber.com> References: <67642B44-7CF3-4F31-9D9A-89D6DEDF66B6@stanleylieber.com> To: 9front@9front.org List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: property-based software hosting On Nov 23, 2016, at 10:45 AM, Marshall Conover wrote:= >=20 > When I was last working on things a month or so ago, I believe the build p= roblem with building go on 9front was related to mismatched type declaration= s; that is, certain types were declared in 9front as being uint_32 or the li= ke, and in go being uint_64, or something of that nature. The details have e= scaped me, but the binaries may be the simplest method, because they're (hop= efully) just plug-and-play. Perform the empirical test. Building on amd64 works fine. Building on 386 is= broken since 1.4.3 and now even building 1.4.2 fails. The trivial fixes men= tioned have not been verified, documented, nor applied upstream. The 386 binaries in question suicide on 9front. Fish and others are well awa= re of this since at least 1.5 but nobody does anything to address the proble= m. We just tell people who don't know any better that everything works great= . Welcome to the Plan 9 community. sl