Go builds on Plan9 suffer from the post-1.9 performance regression.
> On Sep 19, 2019, at 10:29 PM, Steve Simon wrote:
>
> hi,
>
> my plan was to build and run/debug go on a raspberry pi 4 running plan9, not
> to cross compile.
>
> i am confident in the linux cross compile environment i was
hi,
my plan was to build and run/debug go on a raspberry pi 4 running plan9, not to
cross compile.
i am confident in the linux cross compile environment i was just concerned
about the plan9 os/runtime support for the pi.
i guess it comes down to plan9 os interface for the arm.
people said it
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
Building anything on a raspberry pi is a bit of a chore. I highly
recommend running go on your cpu server and/or local to your filesystem.
The generated binaries seem to work fine. I haven't found any bugs, but I
haven't run anything serious on on my pis.
On Thu, 19 Sep 2019, Michael Misch
I’ve used it, it works fine. Building on a raspberry pi, on the other hand is a
chore when using Go.
> On Sep 19, 2019, at 3:46 PM, Bakul Shah wrote:
>
> On Thu, 19 Sep 2019 22:41:48 +0100 Steve Simon wrote:
>>
>> does go run under plan9 on the radpberry pi or only on x86?
>
> I haven't
On Thu, 19 Sep 2019 22:41:48 +0100 Steve Simon wrote:
>
> does go run under plan9 on the radpberry pi or only on x86?
I haven't tried a native build but cross-compiling with
cd `go env GOROOT`/src
GOOS=plan9 GOARCH=arm ./bootstrap.bash
seems to work. bunzip2 the resulting .tbz file in
hi all,
does go run under plan9 on the radpberry pi or only on x86?
thanks,
-Steve
> # when timesync(8) says "$ntp", it's lying.
Actually it's not. But it depends on having a definition
for ntp= associated with your host or [sub]network in the
ndb database.
