From mboxrd@z Thu Jan  1 00:00:00 1970
From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
In-reply-to: <alpine.BSF.2.21.99999.352.1909192321240.5516@silverfox.local>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <69767.1568954244.1@orthanc.ca>
Date: Thu, 19 Sep 2019 21:37:24 -0700
Message-ID: <293bcab7a51132f9@orthanc.ca>
Cc: Lyndon Nerenberg <lyndon@orthanc.ca>
Subject: Re: [9fans] go under plan9 on the radpberry pi?
Topicbox-Message-UUID: 09033ec8-eada-11e9-9d60-3106f5b1d025

Matthew Veety writes:

> Building anything on a raspberry pi is a bit of a chore. I highly=20
> recommend running go on your cpu server and/or local to your filesystem.=20
> The generated binaries seem to work fine.

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.

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 :-(