Date: Fri, 12 May 2000 06:49:07 -0400 (EDT) Message-Id: <200005121049.GAA14368@indy.delorie.com> From: Eli Zaretskii To: Prashant TR CC: djgpp AT delorie DOT com In-reply-to: (message from Prashant TR on Fri, 12 May 2000 11:43:22 +0500 (MVT)) Subject: Re: Bug in tar112a? References: 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 > Date: Fri, 12 May 2000 11:43:22 +0500 (MVT) > From: Prashant TR > > > I got the following errors while trying to extract files. > > ================== > $ tar zxvf /djgpp/zips/sh-utils-2.0i.tar.gz > ... > ... > ... > sh-utils-2.0i/lib/xstrdup.c > sh-utils-2.0i/lib/xstrtod.c > sh-utils-2.0i/lib/xstrtol.c > sh-utils-2.0i/lib/xstrtoul.c > sh-utils-2.0i/lib/xstrtoumax.c > tar: Unexpected end of file in archive > tar: Child returned status 1 > tar: Processed all files possible, despite earlier errors > > =========== > The same thing happens with archives that have many files: > > sh-utils-2.0[ghi].tar.gz. binutils-2.9.1.tar.gz, gcc-2.95.2.tar.gz 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. > The same archives work fine with djtar, however. DJTAR unzips the archive on the fly, so it doesn't need the extra disk space.