From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Installing Go
Date: Fri, 17 May 2013 09:22:06 +0200 [thread overview]
Message-ID: <2f47120625ff266ff494f5419660bb28@proxima.alt.za> (raw)
In-Reply-To: <CAM6ozu4=mPNdo7wSS5L2pM_z5z4ALNg4cPXrmass5NLc+s0yVA@mail.gmail.com>
> If all fails, you can try out what worked for me some time ago:
Building the VERSION file is a minor glitch that seems too much bother
to fix in any practical way: those who have HG installed would in any
case not want it fixed :-(
On the other hand, applying the patch required (and probably by now
insufficient) to compile Go for the ARM is hard to do without HG, so I
suppose that says that we are a bit behind the curve.
I'm hoping to do at least some of the necessary catching up now that
Go 1.1 has been released, but of course the port to plan9/arm is only
one of many issues put on hold ahead of the 1.1 release.
Feel free to ontact me (at my Gmail address <lucio.dere@gmail.com>) if
you have specific issues you want to discuss. Also, there are quite
few developers lurking on go-nuts, that is a good place to make
suggestions as well as to ask questions.
++L
PS: The VERSION file is a permanent version of VERSION.cache that is
generated by the more conventional Go builds. All Go builds delete
VERSION.cache and create a fresh one, unless there is a VERSION file
in which case the latter is used unchanged. What works for me is to
share the GOROOT between NetBSD and Plan 9 and build the NetBSD
version of Go first (I use "tip" normally). Before building on the
Plan 9 servers, I rename $GOROOT/VERSION.cache to $GOROOT/VERSION. I
am convinced that there isn't a mechanism that will please everyone;
I'll be pleased to be proven wrong.
Oh, I also need to delete VERSION before building on NetBSD and
usually I forget to do it :-(
prev parent reply other threads:[~2013-05-17 7:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 22:31 lamg
2013-05-16 22:32 ` Gorka Guardiola
2013-05-16 22:34 ` Gorka Guardiola
2013-05-17 5:07 ` lucio
2013-05-17 6:08 ` Peter A. Cejchan
2013-05-17 7:22 ` lucio [this message]
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=2f47120625ff266ff494f5419660bb28@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).