> To cross compile with make.rc do you just set GOARCH and GOOS and just
run it?
Yes and you can add the --no-rebuild flag to prevent cmd/dist to remove the
existing binaries.
For example:
℅ GOOS=plan9 GOARCH=arm make.rc --no-rebuild
--
David du Colombier
yeah, good points.
On 29 October 2016 at 00:47, yy wrote:
> On 28 October 2016 at 16:23, Mathieu Lonjaret
> wrote:
>> Anyway, does anyone know what the rationale was for choosing to stack
>> them at the bottom? Or why it would be a a bad idea to make them stack
>> at the top instead?
>
> Let's s
I tried this command with both go 1.7.3 and master branches. Both fail right
after “ Building packages and commands for host, plan9/386” with an error
“install: ./install not found.”
It seems like the go bootstrap tool is trying to call a binary called “install”
but there are none on my sys
Heya folks,
Can anyone point me in the right direction of some manuals concerning the use
of a beowulf cluster style of computing setup, i'm so used to MPI installs and
limiting myself to terminals that being what it seems ooout-f-he-box this
already is setup with parallel computing in min
Chris McGee wrote:
>I tried this command with both go 1.7.3 and master branches. Both fail
>right after “ Building packages and commands for host, plan9/386”
>with an error “install: ./install not found.”
>
>It seems like the go bootstrap tool is trying to call a binary called
>“install” but
I would be interested in manuals or papers on this subject as well.
Plan9 is well suited to distributed computing with its per process namespaces
and network transparent resource access. Do grid computing projects built on
plan9 use the built-in OS facilities such as cpu and 9p or do they genera
