From: Marshall Conover <marzhall.o@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] easy install of go on 9front?
Date: Wed, 23 Nov 2016 15:45:09 +0000 [thread overview]
Message-ID: <CAK0pxsGXY3uQn-anPe6PeF9bEnznqJpZ4zrzU90VVUup+OBo1w@mail.gmail.com> (raw)
In-Reply-To: <67642B44-7CF3-4F31-9D9A-89D6DEDF66B6@stanleylieber.com>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
When I was last working on things a month or so ago, I believe the build
problem with building go on 9front was related to mismatched type
declarations; that is, certain types were declared in 9front as being
uint_32 or the like, and in go being uint_64, or something of that nature.
The details have escaped me, but the binaries may be the simplest method,
because they're (hopefully) just plug-and-play.
On Wed, Nov 23, 2016 at 10:39 AM Stanley Lieber <sl@stanleylieber.com>
wrote:
> On Nov 23, 2016, at 5:07 AM, Aram Hăvărneanu <aram.h@mgk.ro> wrote:
> >
> > To install Go on Plan 9 you install it like on any other platform.
> > There is nothing Plan 9 specific about it, and it is easy.
> >
> > --
> > Aram Hăvărneanu
>
> There is the small problem of no git on Plan 9.
>
> sl
>
>
>
[-- Attachment #2: Type: text/html, Size: 1408 bytes --]
next prev parent reply other threads:[~2016-11-23 15:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 9:05 Rudolf Sykora
2016-11-23 10:07 ` [9front] " Aram Hăvărneanu
2016-11-23 11:52 ` Marshall Conover
2016-11-23 15:44 ` Stanley Lieber
2016-11-24 2:01 ` kokamoto
2016-11-24 2:26 ` sl
2016-11-23 15:39 ` Stanley Lieber
2016-11-23 15:45 ` Marshall Conover [this message]
2016-11-23 15:57 ` Stanley Lieber
2016-11-23 15:59 ` Marshall Conover
2016-11-24 21:58 ` Matthew Veety
2016-11-23 15:38 ` Stanley Lieber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAK0pxsGXY3uQn-anPe6PeF9bEnznqJpZ4zrzU90VVUup+OBo1w@mail.gmail.com \
--to=marzhall.o@gmail.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).