Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!mcsun!ukc!axion!uzi-9mm.fulcrum.bt.co.uk!beta.its.bt.co.uk!jvt From: jvt@its.bt.co.uk (John Trickey) Newsgroups: comp.sys.atari.st Subject: Re: Sozobon C and dstart.o <==> Ram Disk Message-ID: <0F^&K3$@uzi-9mm.fulcrum.bt.co.uk> Date: 6 Feb 91 12:02:11 GMT References: <1991Feb4.183344.12478@terminator.cc.umich.edu> Sender: isode@fulcrum.bt.co.uk (Isode Hackers) Organization: BT Applied Systems, Birmingham, UK Lines: 29 In article <1991Feb4.183344.12478@terminator.cc.umich.edu> swood@terminator.cc.umich.edu (Scott Wood) writes: > For a background to what I have set up, I am using gulam as a cli, and >I am using a file called sozo.g to copy the sozobon bin directory and the >sozobon lib directory into the corresponding directories in my RamDisk >(H:) that I set up with rambuffer.acc. I then set paths to h:\sozobon\bin,h:\, >a:\,. and do my work from the a: drive. the ue works fine for my editing, and >then cc main.c gives me the error that it can find the dstart.o file. I >tried cc -IH:\sozobon\lib but that returns the same result. What you need is two more environment variables. LIB=H:\sozobon\lib INCLUDE=H:\sozobon\include or whatever your paths may be. The -I flag tells cc where to find the *.h files. It looks like you are using a single drive system. Before I got a hard disk I was in the same situation. What I did was to keep the binaries libs, etc on A: and copy the source to my RAM Disk. It worked quite well and certainly should reduce the amount of copying needed. John -- John Trickey || ..!mcsun!ukc!axion!its G4REV @ GB7SUT Voice: +44 21 333 3369 #include