[Coco] C compiler crashes VCC with Nitros9

Gene Heskett gheskett at wdtv.com
Fri Oct 4 10:21:16 EDT 2013


On Friday 04 October 2013 10:02:03 Walter ZAMBOTTI did opine:

> Gene Heskett <gheskett at ...> writes:
> > On Thursday 03 October 2013 15:00:24 Bill Pierce did opine:
> > > Gene, He's running straight from the MW distro
> > > CC1 is the front end, you are thinking cc.pass1.
> > > cc1 runs cc.pass1, cc.pass2, c,prep, c.asm, c,opt and c.link in one
> > > swoop.
> > 
> > I figured someone would come along and help me extract my foot. Thank
> 
> you.
> 
> > :)
> > :
> > > His problem is his nitros9 version (3.2.8). and the Vcc emulator.
> > > Vcc and nitros9 3.2.8 had problems getting along for some reason.
> > > Wasn't 3.2.8 the one that sat in the repo for the past 5 years
> > > until it attracted some cockyroaches?
> > 
> > Something like that.  And one of the reasons I keep copy's of old
> > repo's going back to the turn of the century.  And some of that goes
> > back to
> 
> 1993.
> 
> > > I think I remember having a problem in
> > > 3.2.8 with C and that's why I searched and found 3.2.9. Now I got my
> > > custom C setup and I have no problems...
> > 
> > 3.2.9 is several years old, and IMO should have been bumped to 3.3.0
> 
> even
> 
> > before the lwtools conversion was even thought of.  But its not my
> > boat
> 
> to
> 
> > row.
> > 
> > Now its totally confusing as to which code someone has when they say
> 
> 3.2.9.
> 
> > Cheers, Gene
> 
> Thanks for the feed back (Just putting down my coldie now and kind of
> edging back to the coco)
> 
> Where can I find these wonderful compiler tools?
> 
> Where can I find the LATEST version of Nitros9 and the C compiler tools?
> 
> I have an ambitious project to port lwip to the OS-9.  I will need help!
> 
> I may need to add threading support to the kernal but that is not
> entirely necessary because lwip can be configured in a non threading
> OS.
> 
> I may need to write a puesdo network device for VCC and a corresponding
> device driver in OS9.
> 
> I may need to know what is the best filemanager (RBF SCF or my-own) to
> handle network data.  Both seem they could fudge the job but neither
> seems totally suited.
> 
> I was assuming until now that there wasn't a lot of tools out there for
> OS- 9/6809.  I certainly didn't find the C tools Gene mentioned.

If you know what to look for, its all on my site in the Genes-os9-stf link.
See: <http://coyoteden.dyndns-free.com:6309/gene>

> Is there source code repos/distro somewhere?
> 
> Has someone already provided the things I have mentioned (threads, net
> drivers, etc)?

Not really, system ram is the bottleneck.
> 
> regards
> 
> Walter

Walter:  All 3 of the kits that goto making up a current, on your machine, 
(if you are running a linux) copy of whats in todays hg repositories is 
probably best obtained by first installing hg (mercurial) and using it to 
clone the source repositories.

I do this and then once drivewire is up and running, I can generate a new 
boot image using the correct .dsk image mounted in drivewire.  Until then, 
I had to start rz on the coco, and zmodem send the .dsk to the coco's hard 
drive.  Then I had 2 ways to use it. One involved cobbling up a way to 
write that .dsk to a real floppy, or take a spare descriptor and  cobble it 
up to pretend that the .dsk file was a real disk, and dsave it to a 
suitable place on the hard drive so I could run an mb script from there.  
Complex, a PIMA but that is exactly how I got the drivewire bits and pieces 
to the coco.  Once that is working, it is TON's easier.

But that isn't an easy job until DW is running on the coco.
How are you currently moving new code to the coco?  Thats the first 
question.

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)

Most people can do without the essentials, but not without the luxuries.
A pen in the hand of this president is far more
dangerous than 200 million guns in the hands of
         law-abiding citizens.



More information about the Coco mailing list