Message-ID: <001a01bf5d9a$5562d370$293f8589@gv015029.bgo.nera.no>
From: "Gisle Vanem" <gvanem AT eunet DOT no>
To: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Cc: <djgpp AT delorie DOT com>
Subject: Re: bash and /tmp
Date: Thu, 13 Jan 2000 08:46:39 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> said:


>I'm guessing that your TMPDIR either is not set or points to an
>invalid directory.  See section 6.11 of the FAQ.


You're correct.
In plain-DOS I normally have in my djgpp.env "+TMPDIR=f:/" where f: 
is a RAM-disk, but comments that line when running under Win-NT 
where f: is my CD-ROM. IMHO bash should do as gcc does and use 
$TMP or $TEMP in such a case.

>/tmp is probably the last resort, when TMPDIR and some other
>variables aren't set.  You should never get to that point in a
>well-set DJGPP installation (because djgpp.env sets TMPDIR).


Are you saying that bash *requires* a (full) djgpp installatin to work?

Gisle V.