[Coco] Really not understanding how to use DW

Tormod Volden lists.tormod at gmail.com
Mon Sep 30 17:47:37 EDT 2013


On Mon, Sep 30, 2013 at 11:21 PM, Tormod Volden wrote:
> changeset:   2615:530759e9f289
> user:        Boisy Pitre <boisy.pitre at nuance.com>
> date:        Mon Feb 06 15:51:13 2012 -0600
> summary:     Added ccbkrn from Brett Gordon (level 2 only for now)
>
> changeset:   2655:ead54d2c06d4
> user:        Boisy Pitre <boisy.pitre at nuance.com>
> date:        Tue Apr 10 22:25:19 2012 -0500
> summary:     Removed ccbkrn, placed back bra in fnproc.asm
>
> Looks like it was not cleanly removed.

The ccbkrn code is still there, but it is not being built any longer.
I therefore commented out the copying of it.

Now the only real build errors are Dragon related:

$ grep ':.*error' build-dsk.log
copy: error 216 on file 'acia51': pathname not found
attr: error 216 opening 'nos96809l1v030209tano_40s_1.dsk,CMDS/acia51':
pathname not found
copy: error 248 on file 'dragonvtio.d': disk is filled to capacity
copy: error 248 on file 'startup': disk is filled to capacity
attr: error 216 opening 'nos96809l1v030209tano_40s_1.dsk,startup':
pathname not found
attr: error 216 opening 'nos96809l1v030209tano_40s_1.dsk,startup':
pathname not found
copy: error 216 on file 'acia51': pathname not found
attr: error 216 opening 'nos96809l1v030209d64_40s_1.dsk,CMDS/acia51':
pathname not found
copy: error 248 on file 'dragonvtio.d': disk is filled to capacity
copy: error 248 on file 'startup': disk is filled to capacity
attr: error 216 opening 'nos96809l1v030209d64_40s_1.dsk,startup':
pathname not found
attr: error 216 opening 'nos96809l1v030209d64_40s_1.dsk,startup':
pathname not found
copy: error 218 on file 'thexder/ia.fnt': file already exists
copy: error 218 on file 'thexder/ia.fnt': file already exists
copy: error 218 on file 'thexder/ia.fnt': file already exists
copy: error 218 on file 'thexder/ia.fnt': file already exists

The last thexder errors are harmless, but we should get rid of all
errors. IMHO a sane build system should stop on the first error, and I
would eventually like to make nitros9 do it this way. Otherwise errors
go unnoticed and the code rots and falls apart over time.

Tormod



More information about the Coco mailing list