From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20110405043331.GD2000@fangle.proxima.alt.za> References: <20110403211333.GA3905@dinah> <20110403211652.GA5977@dinah> <20110403223031.GA27441@dinah> <20110404172728.GA2000@fangle.proxima.alt.za> <20110405043331.GD2000@fangle.proxima.alt.za> Date: Tue, 5 Apr 2011 09:37:03 +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: c9b26292-ead6-11e9-9d60-3106f5b1d025 On Tue, Apr 5, 2011 at 7:33 AM, Lucio De Re wrote: > No, and no "yuck", either: Go executables are different animals and > they are allowed to be identified as such. =C2=A0Until they are not, when > they are allowed to become the same animal. > snip... > > And maybe it's just me being uninformed, but I have this suspicion that > you need a Go toolchain with Plan 9 targets to produce Plan 9 executables= . > Maybe I should phrase this as a question: does the default Go toolchain > produce Plan 9 executables or is a separate toolchain required for it? > I'm pretty certain there's a need for two toolchains, but I'll be very > happy to be proven wrong (and Ron right, of course). The vanilla Go distribution will produce ELF executables on Linux/FreeBSD/Darwin when the GOOS is set accordingly. If GOOS is set to plan9, 8l will produce a real Plan 9 a.out executable (it might complain it cannot find runtime and other packages unless you follow the procedure to build them). Pavel