From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Misch <michaelmisch1985@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Thu, 19 Sep 2019 22:32:11 -0700
References: <07E8AB88-15C5-4ADB-B22C-311D9A149EF8@quintile.net>
	<20190919224632.33A4A1570CEA@mail.bitblocks.com>
	<63A70485-0D01-4D77-9966-3B4CB758F4CC@gmail.com>
	<alpine.BSF.2.21.99999.352.1909192321240.5516@silverfox.local>
	<293bcab7a51132f9@orthanc.ca>
	<B2EF8F9D-B63C-4F8E-8ACF-3F20436484FD@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
In-Reply-To: <B2EF8F9D-B63C-4F8E-8ACF-3F20436484FD@quintile.net>
Message-Id: <38F68046-AEE8-4675-8850-9DFD5442EC40@gmail.com>
Subject: Re: [9fans] go under plan9 on the radpberry pi?
Topicbox-Message-UUID: 090ece8c-eada-11e9-9d60-3106f5b1d025

Go builds on Plan9 suffer from the post-1.9 performance regression.

> On Sep 19, 2019, at 10:29 PM, Steve Simon <steve@quintile.net> wrote:
>=20
> hi,
>=20
> my plan was to build and run/debug go on a raspberry pi 4 running =
plan9, not to cross compile.
>=20
> i am confident in the linux cross compile environment i was just =
concerned about the plan9 os/runtime support for the pi.
>=20
> i guess it comes down to plan9 os interface for the arm.
>=20
> people said it is painful, you mean the pi is slow?
>=20
> thanks for the help.
>=20
> -Steve
>=20
>> On 20 Sep 2019, at 5:37 am, Lyndon Nerenberg <lyndon@orthanc.ca> =
wrote:
>>=20
>> Matthew Veety writes:
>>=20
>>> Building anything on a raspberry pi is a bit of a chore. I highly=3D20=

>>> recommend running go on your cpu server and/or local to your =
filesystem.=3D20
>>> The generated binaries seem to work fine.
>>=20
>> Go does wonderfully when it comes to generating binaries for
>> non-native architectures.  I have a few Go-based tools I use at
>> work that I build on any number of archictures (macos, freebsd,
>> openbsd, linux / armX, i386, amd64)) that I need to run on one or
>> many of the above.  They all just work.  Makes debugging a breeze.
>>=20
>> But now that they are succumbing to the shared lib/obj doctrine, I'm =
sure
>> I will soon go back to writing C code, since the advantage of those
>> static go binaries is about to be lost :-(
>=20
>=20