[Coco] Microware C Compiler -- issues finding library files

[Stephen H. Fischer]

Ah, you missed the patch to the compiler to change where to look for stuff.

It has been so long (~ Twenty Five years) that I forget what goes where. I can say that a dual 80T 2S floppy system worked great for "C" Compiling.

Then after I got 512K memory the compiler was loaded into memory and the program to be edited into a ram disk and it worked even faster.

Look at this post:

http://www.tandycoco.com/forum/viewtopic.php?p=532#p532

It directs you to the October 1989 Rainbow magazine.

That article in Rainbow from 1989 was where I learned about the patch

SHF

----- Original Message ----- 
From: "Chris Oliver" <chris.w.oliver at me.com>
To: <coco at maltedmedia.com>
Sent: Wednesday, August 12, 2015 9:47 PM
Subject: [Coco] Microware C Compiler -- issues finding library files


> All,
> 
> Two-drive OS-9 scenario — compiler (cc1) in /d1/cmds, LIB and DEFS (including stdio.h) on /d0.  Execution directory set to /d1/cmds.  For the life of me, I can’t figure out how to get the compiler to look on /d0 for LIB and DEFS — and I can’t put everything on /d1 due to space.  Is there a way in OS-9 to pin one of the drives as the “default drive”, such that the compiler will look there vs. on the same drive as the current execution directory?  When I get to the linker, for example, I get a cannot-find error on “/d1/lib/cstart.r” — when, of course, cstart.r is sitting in /d0/lib.
> 
> Many thanks — I’m guessing there is something simple here that I’m overlooking…
> 
> Chris