[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:	AMIGA NOTES
Notice:	Join us in the NEW conference - HYDRA::AMIGA_V2
Moderator:	HYDRA::MOORE

Created:	Sat Apr 26 1986
Last Modified:	Wed Feb 05 1992
Last Successful Update:	Fri Jun 06 1997
Number of topics:	5378
Total number of notes:	38326

1498.0. "Lattice C 4.0 on hard disk?" by VTHRAX::KIP (Explain the Universe and give 3 examples.) Thu Jun 23 1988 17:35

    Being a new, extremely happy hard disk Amiga user, I've been trying
    to install Lattice C (4.01?) on my hard disk, and am getting a strange
    problem.  I'm using 4.0 to which I've applied two patches downloaded
    from the Lattice BBS.  Also, I'm using Conman and Popcli III.
    
    I've been trying to install everything in its own hard disk subdirectory,
    dh2:Lattice_C.  So, I have the following assigns:
    
    LC:		dh2:Lattice_C/c		(contains all the executables)
    LIB:	dh2:Lattice_C/lib	(all the .lib files)
    INCLUDE:	dh2:Lattice_C/CompactH	(all of the compressed headers,
    					 including their subdirectories)
    QUAD:	RAM:			(for the intermediate files)
    DEVEL:	dh2:Lattice_C/devel	(where I keep my sources)
    
    As a minimal test file, I tried to compile and link the following file
    TEST.C: 
    
    void main()
    {
    }
    
    While in the DEVEL: directory, I type: "lc -L test".  I *think* the
    first pass (lc1) of the compiler works ok, then I get the following
    message: 
    
    Parameters after file name ignored
    Can't open quad file
    ...(aborting message)
    
    If I look in RAM:, I see the file test.q; if I invoke lc2 on "test",
    I get the same error msg.
    
    If I copy TEST.C to RAM:, CD to RAM:, then invoke "lc -L test",
    everything works ok!!
    
    Can someone tell me what I'm doing wrong here?
    
    Thanks.

T.R	Title	User	Personal Name	Date	Lines
1498.1		LEDS::ACCIARDI	I Blit, therefore I am...	`Thu Jun 23 1988 17:44`	8
	Some software hardcodes pathnames within the program. I frequently use NEWZAP to go in and edit all occurances of 'df0:bull' to 'dh0:bull' or somesuch. I've used NEWZAP to run Interceptor from my hard drive. I just went in and replaced all the 'df0:' entries with 'dh1:games'. Ed.
1498.2	Still puzzled...	VTHRAX::KIP	No Dukes.	`Thu Jun 23 1988 18:44`	6
	Thanks for the reply. However, aren't Lattice's logical directories (LC:, LIB:, INCLUDE:,etc.) supposed to take care of this? Can't figure out why everything's ok when I work from RAM:, but not from any disk-based directory.
1498.3	no patching required	SAUTER::SAUTER	John Sauter	`Thu Jun 23 1988 19:43`	7
	re: .2, that's correct. I have installed Lattice 4.? (without patches) on my hard disk with no trouble, by following the instructions in the manual. So far I have only executed "hello world", but that's enough to convince me I did it right. Sorry, I don't know why it doesn't work for you. John Sauter
1498.4	Lattice doesn't know why.	VTHRAX::KIP	No Dukes.	`Thu Jun 23 1988 20:12`	7
	Just for the record, I just talked with Lattice Tech Support on this, and they're stumped, too! Going to try omitting my extra utilities one-by-one (Conman, Popcli, etc.) to see if I can find the culprit. Thanks for the help!
1498.5	my two cents	REGENT::VAILLETTE		`Thu Jun 23 1988 20:19`	17
	I have Lattice C installed on my hard drive and all is well, but I do remember having the same problem in the process of getting it installed. I can post my startup-sequence files and listing of C directories tomorrow if you don't get it working. Two things that come to mind right now are: * There was some confusion in my documentation whether LC: should point to dh2:lattice_c or to dh2:lattice_c/c. * You may need PATH RAM: add By the way, I have conman and popcli running while using Lattice C, so that shouldn't be the problem. Gary
1498.6	Cannot handle space	TLE::RMEYERS	Randy Meyers	`Thu Jun 23 1988 21:04`	28
	Re: .0 > Parameters after file name ignored > Can't open quad file > ...(aborting message) Simple problem. The directory path of your source file contains a space. When LC runs LC2, it finds the parent directory of the source file and passes it as a switch argument to LC2. So, if the full name of your source file is: Hard Disk:Development/test.c The command that LC passes to LC2 looks something like: LC2 -oHard Disk:Development test If the space appears in the device part of the directory path, you sometimes get strange requesters. In my example (where the space is in the device), you would get a requester asking you to put "Disk:" in any drive. If the space is in part of the directory, your probably will not get a requester. I think this is a bug. I would like LC to quote names with spaces and for LC1 and LC2 to be able to quoted names names with spaces. Since you have been talking to tech support, I'll let you tell them. :-)