From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] native (mostly) go for plan9
Date: Tue, 1 Nov 2011 09:57:48 -0700 [thread overview]
Message-ID: <CAJSxfmKi-3Z0v+5wTatejiHNGAL8L+mS9K02YdNidicFnLRfww@mail.gmail.com> (raw)
In-Reply-To: <CAP6exYK1SaBpCd2yEwv7o_F7BjisWsO7hr==C08RRFQWFnpG-w@mail.gmail.com>
i pulled the sources about 8 hours ago for another environment and
tried to build. it stops in /go/src/cmd/gotest due to a missing
'mk.go'. inspecting Makefile and mkfile shows that GOFILES includes
'make.go' in Makefile and 'mk.go' in mkfile -- neither exists. i think
this might be an unfinished change. removing the dependency from
mkfile result in a couple of undefined names in gotest.go.
install ../cmd/gotest
INSTALL FAIL ../cmd/gotest
/go/src/pkg
mk: don't know how to make 'mk.go' in directory /go/src/cmd/gotest
mk: echo install ../cmd/gotest ... : exit status=rc 8582: 1
mk: for (i in ... : exit status=rc 272: rc 909: mk 911: error
On Mon, Oct 31, 2011 at 8:11 AM, ron minnich <rminnich@gmail.com> wrote:
> A number of us have been working on a native Go port for plan 9.
>
> The big goal is to do this in a way that makes tracking Go source a
> non-problem, and to eventually just have these changes part of the
> standard Go tree, so there is no work at all.
>
> we're pretty close, thanks to previous work others have done on the Go port.
>
> You can try it.
>
> Right now, due to a few bison and bash dependencies, there are files
> we can not generate. These are supplied as part of the repo.
>
> cd
> hg clone https://code.google.com/p/rminnich-9go go
> bind -ac . /
> cd /go
> cd 9/prebuilt
> rc install
> cd /go/src
> mk install
>
> You've now got all commands and the toolchain. Now you can help us fix this:
>
> goinstall bitbucket.org/rminnich/forth (or any package)
>
> fails with an odd error. use ratrace -c on that command to see what
> sequence produces this error.
>
> Be sure to use the google code tools to mark bugs and submit fixes.
>
> I am going to be doing an update from the main go tree into this repo
> soon. This will likely break things. This working branch will be
> tagged 'audrey'.
>
> thanks
>
> ron
>
>
next prev parent reply other threads:[~2011-11-01 16:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 15:11 ron minnich
2011-10-31 16:41 ` Stanley Lieber
2011-10-31 16:51 ` andrey mirtchovski
2011-10-31 17:08 ` ron minnich
2011-10-31 17:30 ` Stanley Lieber
2011-10-31 17:41 ` andrey mirtchovski
2011-10-31 17:44 ` ron minnich
2011-10-31 17:45 ` Stanley Lieber
2011-10-31 17:50 ` ron minnich
2011-10-31 19:23 ` Stanley Lieber
2011-10-31 19:32 ` ron minnich
2011-10-31 19:44 ` Stanley Lieber
2011-10-31 19:48 ` ron minnich
2011-10-31 21:01 ` ron minnich
2011-10-31 22:10 ` Skip Tavakkolian
2011-10-31 22:17 ` ron minnich
2011-10-31 22:34 ` Bakul Shah
2011-10-31 22:38 ` ron minnich
2011-10-31 22:21 ` ron minnich
2011-11-01 10:20 ` Charles Forsyth
[not found] ` <CAP6exYJ8MQdcRa1vofMVjgaFK0Xu-po4eZBOOb>
[not found] ` <CAP6exYJf1UKFdpeXyFXRt0Y7hPc=Hyq7oBdvi9uX3Z7+FQbxsA@mail.gmail.c>
2011-10-31 22:24 ` erik quanstrom
2011-10-31 22:34 ` cinap_lenrek
2011-10-31 22:44 ` erik quanstrom
2011-10-31 22:47 ` cinap_lenrek
[not found] ` <CAP6exYKue2e7NWx07+RMNDs38aXex0y9urfT6eT1LKbjvvA_yw@mail.gmail.c>
2011-10-31 22:46 ` erik quanstrom
2011-11-01 10:41 ` Yaroslav
2011-11-01 16:57 ` Skip Tavakkolian [this message]
2011-11-01 17:26 ` ron minnich
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=CAJSxfmKi-3Z0v+5wTatejiHNGAL8L+mS9K02YdNidicFnLRfww@mail.gmail.com \
--to=skip.tavakkolian@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).