Re: [9fans] plan9 go output faults on 9vx but ok on cpu

[lucio@proxima.alt.za]

> That plan9 flag works for plan9port?
> Then how I can use it on my linux box with plan9port.

I looked at connecting Go and p9p a few months back, before my
assignments in Cape Town put a halt to my efforts.  My conclusion at
the time was that it was a worthwhile objective that could be
accomplished, but not without a great deal of trouble.  Because of the
scope of the project, I estimated that the chances of getting upstream
approval for the changes, be they to p9p or to Go, would be minimal
despite Russ' involvement in both projects.

Merging p9p, Go and Plan 9 in a portable manner seems to me to be
really hard.  I would be extremely pleasantly surprised if somebody
had achieved even the smallest portion of such merging and had it
pulled up to the source projects.  Also, without carefully
documentation one runs a real risk of having to repeat and sometimes
rediscover many of the changes.  At least, that is the situation I am
confronted by at this very moment.

In a nutshell, I actually took a very recent release of Go and tried
to build a Plan 9 version:

	cd $GOROOT/src
	GOOS=plan9 ./make.bash

I was not surprised that it did not build correctly on my Ubuntu
workstation.  Fixing it did not seem a trivial task and a cursory web
search did not reveal any encouraging help.

Right now, I have a few days in which to resurrect work I did
initially that concluded with a "working" version of the Hello World
"C" program compiled and executed on Plan 9/386 using modifed Go
sources to compile and build the "C" development toolchain under Plan
9.  It is daunting how much effort I estimate I will need to do to get
that far, specially with a view to propagate the rather extensive
changes to the Go source release.  On the positive side, I had
invested no effort in the Go aspects of the project and I'm grateful
to those who have added the Go features for Plan 9 to the Go release.

My regret is that I am so far out of the loop, I don't even know where
the loop is :-(

++L