From: "Peter A. Cejchan" <tyapca7@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Installing Go
Date: Fri, 17 May 2013 08:08:11 +0200 [thread overview]
Message-ID: <CAM6ozu4=mPNdo7wSS5L2pM_z5z4ALNg4cPXrmass5NLc+s0yVA@mail.gmail.com> (raw)
In-Reply-To: <f1dffdecdf0a160f54dcff1526b27c8d@proxima.alt.za>
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
If all fails, you can try out what worked for me some time ago:
version go-93dc7f0e302b compiles out-of the box.
Prerequisites:
kernel post-Aug2012
8* suite post-March2012
VERSION file is needed if hg is not installed.
Mercurial is only needed to generate the top-level VERSION file.
You can work around this by creating the file yourself after
pulling the code from the repository.
Either create a fake VERSION file
echo fake >VERSION
or one that matches what the dist tool would have printed. With sh:
v=`hg log -r tip --template '+{node|short} {date|date}'`
echo devel $v >VERSION
Afterwards you can run tar to generate an archive that can
be moved to any system and built without Mercurial.
Cd to go/src and run:
make.rc
---
++pac
On Fri, May 17, 2013 at 7:07 AM, <lucio@proxima.alt.za> wrote:
> To Gorka, specially, but anybody else who may wish to know:
>
> > Sorry, you also need to get the tip (use hg to get the
> > latest without saying you want a release)
> > In arm you will need lucio´s patch.
>
> I've been caught up in a lot of different things and haven't been able
> to focus on Go for Plan 9, but I'll try to re-focus in the next few
> days.
>
> I'll try out the 1.1 release as soon as I get a chance and report back
> here with the outcome.
>
> ++L
>
>
>
[-- Attachment #2: Type: text/html, Size: 1807 bytes --]
next prev parent reply other threads:[~2013-05-17 6:08 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 [this message]
2013-05-17 7:22 ` lucio
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='CAM6ozu4=mPNdo7wSS5L2pM_z5z4ALNg4cPXrmass5NLc+s0yVA@mail.gmail.com' \
--to=tyapca7@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).