Date: Fri, 12 May 2000 18:15:26 +0500 (MVT)
From: Prashant TR <prashant_tr AT yahoo DOT com>
X-Sender: tr AT vsnl DOT net DOT in
To: Eli Zaretskii <eliz AT delorie DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Bug in tar112a?
In-Reply-To: <200005121049.GAA14368@indy.delorie.com>
Message-ID: <Pine.LNX.4.10.10005121807110.919-100000@vsnl.net.in>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On Fri, 12 May 2000, Eli Zaretskii wrote:

> What is the size of the disk where TMPDIR points?
> 
> Tar runs gzip via `popen', to unzip the archive; `popen' redirects
> gzip's output to a temporary file.  If TMPDIR points to a RAM disk or
> any other place where there's not enough space for holding the entire
> unzipped archive, you will get this error.
> 
> As a rule of thumb, you need to make sure that TMPDIR has enough free
> space to hold 4 times the compressed archive.  For large packages such
> as GCC you will need about 40-50MB.
> 
> This is all explained in README.djgpp file that comes with the
> distribution, btw.

It works fine now. Thanks. My TMPDIR was pointing to a RAM drive. I
changed to %DJDIR%/tmp and it solved the problem.

Prashant