[Coco] Coco Digest, Vol 49, Issue 23

[Paul Fitch]

> 
> Message: 17
> Date: Mon, 6 Aug 2007 22:49:58 -0400
> From: "Shain Klammer" <sklammer at gmail.com>
> Subject: [Coco] GCC for the Coco
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Message-ID:
> 	<3925f0b0708061949x7bb5ae45v89e31471279d2310 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Some of you may not know this yet, but GCC has made it to the 6809
> (http://www.oddchange.com/gcc6809/), here are the last couple of news
> entries...
>  and this site (http://skwirl.net/coco/gcc.html) had started something
> specifically for developing to the Coco... I haven't read them myself
> yet; but, here you go...
> 
> sk
> 
> July 31, 2007
> 
> The GCC 6809 blog is unveiled. Not much here yet but this seems a good
> way to get out more information as time goes on.
> 
> June 10, 2007
> 
> A new stable version of gcc 3.4.6 for the 6809 has been tagged in
> Subversion. The repository path is gcc6809/tags/2007-06-10.
> 
> In addition, the branches/gcc4.1 version of the compiler has been
> updated so that it works with the latest, mainline version of GCC
> (what will become GCC 4.3.0). Although it appears to work fine and has
> passed most of the GCC testcases, it is still not considered ready for
> primetime yet.
> 
> See the Status section below for an overview of the changes.
> 
> 
And where is the friggin binary?  Not there.  The feeling I get is "if they
can't figure out how to compile it, they shouldn't be using it."

I fail to see how wanting to use a C compiler first requires me to be up to
speed enough to compile the scumbag.

NOTE: If I'm coming across kinda negative in the last few posts, its because
I've been banging my head against some walls here.  You guys are used to the
walls, you just walk around them.