[Coco] C compiler question
bdevries at gil.com.au
Sat Dec 24 01:20:58 EST 2005
Answering my own question here....
If I add #32k to the command line of CC, it works fine. I don't understand
why, though, since the programme source isn't large, and doesn't use much
memory for variables.
Regards, Bob Devries, Dalby, Queensland, Australia
Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.
my blog: http://bdevries.invigorated.org/
----- Original Message -----
From: "Bob Devries" <bdevries at gil.com.au>
To: <coco at maltedmedia.com>
Sent: Saturday, December 24, 2005 4:16 PM
Subject: [Coco] C compiler question
> It's been too long since I've written and compiled any C code for the
> Coco-OS9. SIGH.
> I've written a programme, and I'm compiling it with CC v2.5.2. It gets all
> the way to the linker stage, and quits with 'unresolved references'
> Unresloved references:
> _7 creatdsk_c in ctmp.3.r
> _28 creatdsk_c in ctmp.3.r
> _18 creatdsk_c in ctmp.3.r
> _13 creatdsk_c in ctmp.3.r
> Can anyone tell me what's going on here? Surely these references are
> produced by the compiler itself? Is this a memory allocation issue?
> I'm doing this on MESS V102 using NitrOS9/6309(50Hz) V03.02.05
> Regards, Bob Devries, Dalby, Queensland, Australia
> Isaiah 50:4 The sovereign Lord has given me
> the capacity to be his spokesman,
> so that I know how to help the weary.
> website: http://www.home.gil.com.au/~bdevasl
> my blog: http://bdevries.invigorated.org/
> Coco mailing list
> Coco at maltedmedia.com
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.371 / Virus Database: 267.14.7/214 - Release Date: 23/12/2005
More information about the Coco