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

[Chris Oliver]

Stephen, Gene, Robert, and Bill —

Many, many thanks for your help and advice!  We’re all set now.  I still find it hard to believe that I can post a question about a 32-year-old compiler, and get several detailed answers like this.  :)  (And that a couple of you literally knew about the 1989 Oct Rainbow article.)

And Bill — you weren’t kidding.  Compiling one of the sample sources (a simple 19-line program) took a full 5 minutes!  Wow.

Thanks again, and long live the CoCo —

Chris

> On Aug 13, 2015, at 12:47 AM, Chris Oliver <chris.w.oliver at me.com> wrote:
> 
> 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