From: Kenny Lasse Hoff Levinsen <kennylevinsen@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go on Plan 9?
Date: Tue, 26 Jan 2016 23:03:08 +0100 [thread overview]
Message-ID: <616318C6-81ED-4F6B-AE82-87EBECDE97D3@gmail.com> (raw)
In-Reply-To: <b58a643b7a3bb04f750bea09f517b98a@habu.attlocal.net>
Go builds just fine right now on the plan9 builders: http://build.golang.org
1.4 and 1.5 are very different, due to 1.5 being written in Go. i386 and amd64 should both build, although amd64 fails an irrelevant unittest.
What do you see with 1.5.2/1.5.3? (You said you tried?)
Best regards,
Kenny Levinsen // joushou
> On 26 Jan 2016, at 22:52, sl@9front.org wrote:
>
> From http://fqa.9front.org/appendixl.html:
>
> # automatically converted ca certs from mozilla.org
> hget http://curl.haxx.se/ca/cacert.pem >/sys/lib/tls/ca.pem
> # shell script that emulates git commands
> hget http://9front.org/extra/rc/git >$home/bin/rc/git
> chmod 775 $home/bin/rc/git
> # fetch the repository
> git clone https://go.googlesource.com/go
> cd go
> git checkout go1.4.2
> # build go
> cd src
> ./make.rc
> # install documentation
> go get golang.org/x/tools/cmd/godoc
> # go!
>
> Newer versions of go seem to have problems with Plan 9.
>
> sl
>
next prev parent reply other threads:[~2016-01-26 22:03 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 21:52 sl
2016-01-26 22:03 ` Kenny Lasse Hoff Levinsen [this message]
2016-01-26 22:29 ` sl
2016-01-26 22:38 ` David du Colombier
2016-01-27 1:29 ` Matthew Veety
-- strict thread matches above, loose matches on Subject: below --
2016-04-12 0:59 Chris McGee
2016-04-12 19:01 ` Skip Tavakkolian
2016-04-12 19:21 ` Chris McGee
2016-04-12 19:50 ` Dave MacFarlane
2016-04-12 21:26 ` Skip Tavakkolian
2016-04-13 0:18 ` Chris McGee
2016-04-12 21:44 ` sl
2016-04-13 2:50 ` Skip Tavakkolian
2016-04-13 2:59 ` Chris McGee
2016-04-13 7:27 ` lucio
2016-04-13 9:10 ` Richard Miller
2016-04-13 9:10 ` Richard Miller
2016-04-13 13:08 ` Chris McGee
2016-04-13 13:46 ` Richard Miller
2016-04-13 14:00 ` Chris McGee
2016-04-13 14:32 ` Kenny Lasse Hoff Levinsen
2016-04-13 14:32 ` Charles Forsyth
2016-04-13 14:39 ` Richard Miller
2016-04-13 14:42 ` Charles Forsyth
2016-04-13 14:46 ` Richard Miller
2016-04-13 14:46 ` Charles Forsyth
2016-04-13 14:52 ` lucio
2016-04-13 16:12 ` Richard Miller
2016-04-13 7:21 ` lucio
2016-04-13 7:34 ` lucio
2016-04-13 20:38 ` Skip Tavakkolian
2016-01-26 21:44 Sean Caron
2016-01-26 22:05 ` Skip Tavakkolian
2016-01-26 22:16 ` Sean Caron
2016-01-26 22:32 ` David du Colombier
2016-01-26 22:40 ` David du Colombier
2016-01-27 1:40 ` Sean Caron
2016-01-27 1:52 ` Skip Tavakkolian
2016-01-27 2:24 ` Sean Caron
2016-01-27 4:04 ` lucio
2016-01-27 6:25 ` David du Colombier
2016-01-27 13:45 ` Charles Forsyth
2016-01-26 22:19 ` David du Colombier
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=616318C6-81ED-4F6B-AE82-87EBECDE97D3@gmail.com \
--to=kennylevinsen@gmail.com \
--cc=9fans@9fans.net \
/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).