[Coco] OS9 C compiler

[Dave Philipsen]

Ah, yes, I think I understand now.  It looks like there are multiple 
files that need to be compiled together and I'm lacking the one with main().

Thanks



On 5/6/2017 4:45 AM, James Jones wrote:
> cstart is the code that sets up things that C programs expect (zeroing or
> initializing file scope and static variables, setting up stdio for standard
> in/out/error, converting what the target OS uses for command line arguments
> into argc/argv), calls main, and then does whatever teardown C programs
> expect (e.g. closing standard input, output, error, for ANSI calling
> functions registered with atexit()) and exits the process, passing the exit
> code returned from main() or passed to exit() back to the operating system
> so the parent process can see how things turned out..
>
> The important part here is that it calls main(). That's the reference that
> isn't resolved. Whoever wrote the code didn't include main(), which a
> complete C program has to have. Maybe whoever wrote the code intended it to
> be used as a library?
>
> On Fri, May 5, 2017 at 11:31 PM, Dave Philipsen <dave at davebiz.com> wrote:
>
>> Any OS9 'C' gurus out there that could help me with a problem?
>>
>> I'm compiling some code written by someone else and my command line looks
>> like this:
>>
>> cc1 csc.c -DOS9 -DX6809
>>
>> The compiler proceeds through both passes, the optimizer and the assembler
>> but it chokes on the linker with this error:
>>
>> Unresolved references:
>>   main                        cstart_a                 in /dd/lib/cstart.r
>> linker fatal: unresolved references
>>
>>
>> Any clues?
>>
>>
>> Dave
>>
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> https://pairlist5.pair.net/mailman/listinfo/coco
>>