From mboxrd@z Thu Jan 1 00:00:00 1970 From: smiley@zenzebra.mv.com To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> References: <86ipx4s36p.fsf@cmarib.ramside> <20110201062624.GA1997@fangle.proxima.alt.za> Date: Tue, 1 Feb 2011 07:07:30 +0000 In-Reply-To: <20110201062624.GA1997@fangle.proxima.alt.za> (Lucio De Re's message of "Tue, 1 Feb 2011 08:26:24 +0200") Message-ID: <8662t4s05p.fsf@cmarib.ramside> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: lucio@proxima.alt.za Subject: Re: [9fans] RESOLVED: recoving important header file rudely Topicbox-Message-UUID: a6140408-ead6-11e9-9d60-3106f5b1d025 Lucio De Re writes: > Also, you have managed to stomp all over a couple of this mailing list's > most sacred cows with your suggestion that the Plan 9 kernel code is less > than perfect Ooh! No intent to offend. I actually haven't even looked at the kernel code, yet. I was referring to the bits under /sys/src/cmd/. > _my_ suggestion to you is that you port the code to GCC and do what > you like with it there. You mean port the userspace to GCC? Or the kernel? Wouldn't that kind of defeat the intent behind Plan 9's redesigned toolchain? Is gcc even supported enough on Plan 9 for serious work? The docs I've read seem to suggest that gcc is kind of "glued onto the side of" Plan 9 proper. > Chances are that the the changes you want to introduce are going to be > incompatible in some or other manner; Some, yes. But most not. At least not yet. :) I expect I might run into trouble figuring out how to pass around strings containing NUL bytes, though.