On Sun, Apr 03, 2011 at 07:50:20PM +0100, Steve Simon wrote: > > A month or so ago I got the go compiler chain to build on plan9, > port is too grand a term, it was just fixing a few nits. > That makes a third version. I seem to remember Erik's version compiled clean and I have to ask Steve now whether his version actually generates Plna 9 executables. And, for that matter, how far the Go portion reached.
The version I have restricts itself to C, but has libraries generated using the Go toolchain and has produced one non-trivial object code that ran successfully. Regarding the Go compiler and runtime, I seem to remember that gc.a was created, but nothing else. > I wrote mkfiles and fixed a few minor bugs. The bigest problem was my > knowledge > of yacc was not sufficent to rework the error generation magic go uses from > the bison based code to plan9 yacc code. perhaps there is a yacc expert out > there > who would be interested in helping? > When I looked at the Go sources, no such magic stood out, but it's a long time ago and I may have ignored the problem intentionally. > I am happy to push back my changes, but without either getting yacc to work, > or, > abandoning yacc and porting bison, I didn't feel it was ready. > Maybe Erik, Steve and I should consolidate our changes into a single batch and submit it as a unit, knowing that it will have received at least some competent code review. Anybody else who may want to contribute would, in my view, be welcome. Reviewing code intended for Plan 9 cannot be terribly high within the Google framework at this point in time. ++L
