[comp.sys.amiga] Trouble compiling

dave@dms3b1.UUCP (Dave Hanna) (11/05/88)

Okay, I know I'm showing my ignorance and inexperience here,
but I'd rather ask for help than spend weeks trying to figure
this out myself.  I'm starting to do my first real C compiles
on the Amiga, and I'm using Lattice V3.03 (the one that came with
the old developers kit), plus BLink and a make program I got from
a local BBS.  I have a two floppy A2000 with 1 Meg.  I have 'make'
in RAM:, my source code disk in df0:, and my lattice c disk with
include files in df1:.  Most of the Standard System devices (e.g.,
C:, FONTS:, LIBS:, DEVS:, etc.) are assigned to a disk labeled
'System:', which I usually keep in drive 1.

Question:  Whenever make or LC attempt to load another program,
I get a requestor for 'Volume System:', even if the path name
for the program that is being loaded is fully specified (e.g.,
when make  attempts to load 'LATTICE:c/LC', or when LC attempts to
load 'LC:LC1', where LC has been assigned to LATTICE:c ).
I tried assigning C: to RAM:, and then I get messages 
that the program fails with code 1.  What is it that 
is being looked for on System: ?  I'm sure you don't need a 
THREE drive system to do compiles.

Any help would be appreciated.
    Dave Hanna
-- 
Dave Hanna,  Daltech MicroSystems    |  "Do or do not -- There is no try"
P.O. Box 584, Bedford, TX 76095      |                        - Yoda
(214) 358-4534   (817) 540-1524      |
UUCP:  ...!killer!gtmvax!dave        |

fgd3@jc3b21.UUCP (Fabbian G. Dufoe) (11/07/88)

From article <157@dms3b1.UUCP>, by dave@dms3b1.UUCP (Dave Hanna):
> on the Amiga, and I'm using Lattice V3.03 (the one that came with
> the old developers kit), plus BLink and a make program I got from
> a local BBS.  I have a two floppy A2000 with 1 Meg.  I have 'make'

     I can't answer your specific questions but I would strongly urge you
to upgrade your compiler to version 4.01.  Version 3.03 was awkward to work
with.  Version 3.10 and subsequent ones are much better.  For example, with
version 3.03 there was no compile command, just an execute file that ran
through the two compile commands (lc1 and lc2).  The later versions
introduced the lc command which was capable of invoking both lc1 and lc2 as
well as the linker.

--Fabbian Dufoe
  350 Ling-A-Mor Terrace South
  St. Petersburg, Florida  33705
  813-823-2350

UUCP: ...codas!usfvax2!jc3b21!fgd3 
      ...uunet!pdn!jc3b21!fgd3