Date: Sun, 12 Jul 1998 19:07:13 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Nate Eldredge <nate AT cartsys DOT com>
cc: "John M. Aldrich" <fighteer AT cs DOT com>, djgpp-workers AT delorie DOT com
Subject: Re: Compile gives Abort! error
In-Reply-To: <35A6687B.661DBBFA@cartsys.com>
Message-ID: <Pine.SUN.3.91.980712190658.27114C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Fri, 10 Jul 1998, Nate Eldredge wrote:

> > You need to set the TMPDIR environment variable to point to a writable
> > location.  By default, DJGPP will use f:/djgpp/tmp for the temp
> > directory, which won't work since you say that f: is read-only.  TEMP
> > and TMP aren't used by DJGPP.
> 
> I wonder: why not?  Seems to me we could just set TMPDIR to TEMP in
> DJGPP.ENV.  Since DOS users have to have TEMP set reasonably anyhow,
> that would save trouble of this kind.

There's nothing wrong with a systen where TEMP is unset.  It is true
that most systems have it set, but we cannot count on that.  Remember
that bug with the stub which assumed that PATH is always non-empty?

It is okay IMHO to have DJGPP.ENV use TEMP or TMP if they are set, but
we need a fallback in case they aren't.

Also, please note that TEMP is usually set to a directory on a real
disk, while TMPDIR is best pointed to a RAM disk, if you have one.