kobetitsch@picker.picker.com (harry kobetitsch) (04/24/91)
I have the following question: If I have a machine running all development tools from Interactive Workstation Developer Package on machine A, and I am logged into machine B that has the complete filesystem from machine a mounted via NFS, how do I redirect default libraries, includes, etc when using cc. Right now, it is looking for libraries in /lib, default routines like ld in /bin and includes in /usr/include. The files are in /machineA/bin,/machineA/lib, /machineA/usr/include, etc. I know one solution is to set certain flags like -Y in cc but is there a way to set some kind of environment variables so I don't have to use the flags all the time? P.S. Interactive could not give me a decent answer on this. -- Harry Kobetitsch (216)-473-2624 Picker International, Inc. 595 Miner Rd, Highland Heights, OH 44143 (UUCP: ...!uunet!picker!kobetitsch) (Internet: kobetitsch@picker.com)
dag@gorgon.uucp (Daniel A. Glasser) (04/27/91)
In article <257@picker.picker.com> kobetitsch@picker.picker.com (harry kobetitsch) whines: >I have the following question: >If I have a machine running all development tools from Interactive >Workstation Developer Package on machine A, and I am logged into >machine B that has the complete filesystem from machine a mounted >via NFS, how do I redirect default libraries, includes, etc when using >cc. Right now, it is looking for libraries in /lib, default routines >like ld in /bin and includes in /usr/include. The files are in >/machineA/bin,/machineA/lib, /machineA/usr/include, etc. >I know one solution is to set certain flags like -Y in cc >but is there a way to set some kind of environment variables >so I don't have to use the flags all the time? > >P.S. Interactive could not give me a decent answer on this. There is a file in /bin of the machine on which the SDS is installed called gencc. There is a man page for it. Its job is to create a front end for cc which changes the defaults for all of those things. Use it and put the resulting cc front end in your local path somewhere. That should take care of it for you. (This is true of the SDS that came with ISC 2.2, I don't remember if it was in 2.0.2 or earlier, and the man pages were not on-line with 2.0.2.) Daniel A. Glasser -- Daniel A. Glasser One of those things that goes dag%gorgon@persoft.com "BUMP! (ouch!)" in the night.