From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 10 Apr 2011 09:28:42 +0300 Message-ID: From: Pavel Zholkover To: lucio@proxima.alt.za, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] Go Plan 9 Topicbox-Message-UUID: ce81849c-ead6-11e9-9d60-3106f5b1d025 The following executables are installed into $GOROOT/bin as Plan 9 a.out binaries when you run make -k install inside src/pkg: cgo, ebnflint, gofix, gofmt, gotest, gotype, govet, goyacc, hgpatch. They should be directed somewhere else by setting GOBIN, there is no need to include them in your PATH, the host's native executables are already in place after you build Go. There is a temporary fix to the mmap issue with pkg syscall in my patch queue, it just moves the mmap staff over to syscall_unix.go. Pavel On Sun, Apr 10, 2011 at 8:07 AM, Lucio De Re wrote: >> The new build incantation is: >> >> cd $GOROOT/src/pkg >> make clean >> mkdir -p $GROOT/bin/plan9 >> GOOS=3Dplan9 GOBIN=3D$GOROOT/bin/plan9 make -k install > > I won't try this until the mmap problem you refer to is resolved, so a > question is in order: are the plan 9 tools essential to the operation > of 8l with GOOS=3Dplan9 and will they be found by default or will one > need to make sure that the PATH is set to find them ahead of the Linux > ones? > > Wait. =C2=A0You are talking about a.out executables, these are specifical= ly > for the Plan 9 environment, aren't they? =C2=A0I guess I need to look for > myself :-) > > Alternatively, is it sufficient to specify a different GOBIN or does > the PATH need to be changed? =C2=A0I think I know the answer to this > question is that the PATH needs changing, but I am normally wrong in > these matters. > > ++L > > >