From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <63064D18-61F9-4B5C-8F88-2EC793E1A558@corpus-callosum.com> References: <63064D18-61F9-4B5C-8F88-2EC793E1A558@corpus-callosum.com> Date: Tue, 3 Dec 2013 09:46:34 +0000 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7bb03e780c81f404ec9e2ccf Subject: Re: [9fans] Go and 21-bit runes (and a bit of Go status) Topicbox-Message-UUID: 91084e8c-ead8-11e9-9d60-3106f5b1d025 --047d7bb03e780c81f404ec9e2ccf Content-Type: text/plain; charset=UTF-8 On 3 December 2013 08:14, Jeff Sickel wrote: > See https://codereview.appspot.com/15750047 as it gets around the > issue w/o using the current go supplied but the Plan 9 > go has its own bio, used by its self-contained source tree. why can't it just use the one it expects? i think you explained it once, but i've reverted to being mystified. --047d7bb03e780c81f404ec9e2ccf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 3 December 2013 08:14, Jeff Sickel <jas@corpus-callosum.com&g= t; wrote:
S= ee ht= tps://codereview.appspot.com/15750047 as it gets around the
issue w/o using the current go supplied <bio.h> but the Plan 9

go has its own bio, used by its self-contained so= urce tree.
why can't it just use the on= e it expects?
i think you explained it once, but i've reve= rted to being mystified.
--047d7bb03e780c81f404ec9e2ccf--