[Coco] os-9 cc errors

[Bill Pierce]

I forgot Ed was level 2 ... sorry

Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Bill Pierce
ooogalapasooo at aol.com




-----Original Message-----
From: Retro Canada <retrocanada76 at gmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Thu, Oct 25, 2012 12:18 am
Subject: Re: [Coco] os-9 cc errors


the Ed i have doesn't work, it shows blue screen and all characters are dots :(

On Thu, Oct 25, 2012 at 12:12 AM, Bill Pierce <ooogalapasooo at aol.com> wrote:
>
> Try this, if you're editing in windows, load the text into notepad, then just 
resave it. Then transfer it to OS9 in whatever way you choose, load into Ed 
(3.0) And then save it again. It should compile then. I have to do this quite 
often, especially with stuff from the Nitros9 repo. Notepad seems to take out 
any non-standard chars and Ed finishes it by putting it into os9 format. I also 
have to do the Ed load and save with stuff I edit in RainbowIDE as well.
>
> Hope it helps
> Bill P
>
> Music from the Tandy/Radio Shack Color Computer 2 & 3
> https://sites.google.com/site/dabarnstudio/
> Bill Pierce
> ooogalapasooo at aol.com
>
>
>
>
> -----Original Message-----
> From: Retro Canada <retrocanada76 at gmail.com>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Wed, Oct 24, 2012 11:54 pm
> Subject: Re: [Coco] os-9 cc errors
>
>
> hi i got the error, the carriage return and linefeed from windows that
> os-9 doesn't like :P
>
> i need to replace to CR every time :( this sux!
>
> don't want to edit the text on coco, i'm not crazy, and I use a
> overclocked VCC to compile it.
>
> Is there a cross-c compiler for os-9 ? I found a gcc6809 but it is RSDOS only 
:(
>
>
> On Wed, Oct 24, 2012 at 11:40 PM, Gene Heskett <gheskett at wdtv.com> wrote:
>> On Wednesday 24 October 2012 23:39:21 Retro Canada did opine:
>>
>>> hi,
>>>
>>> i'm trying to use the C compiler for nitrOs-9 but it is stupid cause
>>> it floods the screen with compiling errors and I don't see any option
>>> to either stop at first error or to pause the screen. so I can't see
>>> where is the first error. Even cc code.c > out doesn't work cause the
>>> errors are not piped !
>>>
>>> how do you do it guys ?
>>>
>>> thx
>>
>> tmode .1 pau=1
>> in the window/shell you run the compiler in.  That gets you 1 screen full
>> of data per keyboard tap.
>>
>> Now, post the first error please.
>>
>> Cheers, Gene
>> --
>> "There are four boxes to be used in defense of liberty:
>>  soap, ballot, jury, and ammo. Please use in that order."
>> -Ed Howdershelt (Author)
>> My web page: <http://coyoteden.dyndns-free.com:85/gene> is up!
>> The first time, it's a KLUDGE!
>> The second, a trick.
>> Later, it's a well-established technique!
>>                 -- Mike Broido, Intermetrics
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>
>
> --
> Panasonic FSA1-WSX
> Commodore 64
> Commodore 64C
> Commodore 128
> Apple //c
> TRS-Color Computer 3
> TI-99/4A
> ..and more coming!
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco



-- 
Panasonic FSA1-WSX
Commodore 64
Commodore 64C
Commodore 128
Apple //c
TRS-Color Computer 3
TI-99/4A
..and more coming!

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco