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

[Gene Heskett]

On Thursday 13 August 2015 07:19:44 Chris Oliver wrote:

> Gene,
>
> I have the 1983 Microware C Compiler, version 1.0, cat number 26-3038
> distributed by Radio Shack.  Comes on 2 floppies: one has the
> compiler, the other has the libraries.
>
> Thank you!
>
> Chris

That one does have a pretty good vacuum, but its editable.  So are the 
makefiles if you want to use T.K.'s make. More complex of course, but 
that really is the right way to go once the concepts are absorbed.
>
>
> Generally, those options are set in the compilers driver script.  You
> didn't say which one, and there are several variations extant.
>
> Cheers, Gene Heskett
> --
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page <
> http://geneslinuxbox.net:6309/gene
>
> > 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


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>