[comp.sys.amiga.tech] Lattice 5.02 help needed

840445m@aucs.uucp (Alan McKay) (10/22/89)

I have recently upgraded to Lattice 5.02 from 4.0 and am having a problem.
My setup is as follows.  I have one generic boot disk that I use no matter
what kind of work I will be doing (programming, word processing, etc).  On
this disk I have shell scripts that will set up the appropriate environment
according to what I want to do.  My "lattice" script does the following:

	assign LD:      Lattice_DOS:
	assign WRK:     LD:wrk
	assign QUAD:    RAM:
	assign LC:      LD:lc
	path   LC:      add
	assign INCLUDE: Lattice_LIBS:CompactH 
	assign LIB:     Lattice_LIBS:lib

"Lattice_LIBS" is simply an unmodified Lattice disk #2.  "Lattice_DOS" is
a disk with two directories, one called "work" with all of my source code
and one called "lc" with all of the Lattice commands.  The setup is 
exactly as it has always been and has worked fine until 5.02 came along.
When the new compiler came I changed "Lattice_LIBS" to the new Disk #2
and changed all of the commands in "Lattice_DOS:lc" to the new versions.
I also added the new "lse" and support files that it needs.  Here is what
is in the "lc" directory .... blink, lc, lc1, lc2, lcerrs.txt, lse, lse.dat
lse.hlp, lse.msg.

Now the problem.  I first noticed it when trying to use "F4" to compile
from within LSE.  Nothing would happen.  I later noticed that a compile
message came up but lack of disk activity clued me in that the compile
was not taking place.  I then tried to compile from outside of LSE.  I
tried invoking the "lc" command directly.  I get the copyright notice
from lattice, then "compiling blah.c" message comes up, but I get
"total files 'x',  Compiled OK 0, Failed to compile 'x'"
This code is unchanged from when it used to compile with 4.0.  Furthermore,
I get no error messages.  But then I tried to compile separately by 
invoking "lc1" and "lc2" on their own and everything worked just fine.
I don't understand what is wrong.  Any help would be greatly 
appreciated.  Oh, also, I tried everything out by booting with Lattice
Disk #1 and having #2 in my second drive.  Everything works fine.  The
only thing I can figure is something has changed that doesn't like my
environment, I would really like to know what!
-- 
+ Alan W. McKay       +                                               +
+ Acadia University   +  "Courage my friend, it is not yet too late   +
+ WOLFVILLE, N.S.     +   to make the world a better place."          +
+ CANADA              +                 -Tommy Douglas                +