This is due to something bad that happened in my fusion (which has at
this point totally gone away -- blown venti).

I just fixed it, go ahead and give it another try.

ron

On Tue, Nov 1, 2011 at 9:57 AM, Skip Tavakkolian
<[email protected]> wrote:
> 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 <[email protected]> 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
>>
>>
>
>

Reply via email to