From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] mercurial poisoning
Date: Mon, 15 Apr 2013 06:21:36 +0200 [thread overview]
Message-ID: <58c97d8f1de4f8e697a9a7771e5f976a@proxima.alt.za> (raw)
In-Reply-To: <CAJSxfmJZ6TUmSe75=Vi6JxNFHaaKqwp8801aou00x=WiEEOgyw@mail.gmail.com>
> go tool dist: FAILED: /bin/hg identify -b:
> '/n/zotac/usr/local/go/VERSION.cache' does not exist
> cpue%
If you have a VERSION file (not VERSION.cache), the build won't look
for VERSION.cache, nor try to build it. It's not the ideal solution,
nor is aliasing hg to "echo" with some arbitrary string as argument.
I tend to build Go on the host computer, specially after a recent "hg
sync" (or "hg pull"), then reanme VERSIOn.cache to CACHE. If you
delete VERSION* before the build:
$ cd $GOROOT/src
$ rm -f $GOROOT/VERSION
$ ./all.bash &&
mv $GOROOT/VERSION.cache $GOROOT/VERSION
then subsequent Plan 9 builds will work.
Also, while you're at it, add an arbitrary "echo" at the end of
make.rc and remove the leading dot in ". ./make.rc" in all.rc to
allow the procedure to run without interruption. The tests are still
incomplete, though, in my experience.
++L
PS: This works for me for 386 and arm. Let me know if you encounter
any further problems, by now I ought to know all possible tricks :-)
prev parent reply other threads:[~2013-04-15 4:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-14 19:27 Skip Tavakkolian
[not found] ` <CA+db=n1c-aA=N9Zj+dJ5kjup_07C3kp_QxEMjSkhoohZBSU_MQ@mail.gmail.com>
2013-04-14 21:53 ` [9fans] [go-nuts] " Skip Tavakkolian
2013-04-14 22:30 ` andrey mirtchovski
2013-04-14 23:05 ` Skip Tavakkolian
2013-04-15 4:21 ` 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=58c97d8f1de4f8e697a9a7771e5f976a@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).