Newsgroups: comp.os.msdos.djgpp
Date: Thu, 6 Feb 1997 23:12:28 -0600 (CST)
From: "Colin W. Glenn" <cwg01 AT gnofn DOT org>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc: "John M. Aldrich" <fighteer AT cs DOT com>,
        Gurunandan R Bhat <grbhat AT unigoa DOT ernet DOT in>, djgpp AT delorie DOT com
Subject: Re: tar for DJGPP | Followup:
In-Reply-To: <Pine.SUN.3.91.970205172821.2719H-100000@is>
Message-ID: <Pine.GSO.3.95.970206230634.6680B-100000@sparkie.gnofn.org>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 970205172821 DOT 2719H-100000 AT is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 5 Feb 1997, Eli Zaretskii wrote:
> On Tue, 4 Feb 1997, Colin W. Glenn wrote:
> > > None.  Do you really want your precious sources to be quitely dumped to 
> > > Kingdom Come?
> > 
> > I'm not sure I follow, how so?
> 
> DJTAR was created to handle Unix-born tar files.  Those tar files include
> files whose filenames are illegal on MSDOS, or clash with one another
> within the restricted 8+3 DOS namespace.  When a clash happens which DJTAR
> cannot resolve by itself, it prints a message and asks what to do.  Making
> DJTAR shut up would prevent you from knowing that something went wrong, so
> you wind up with some of the files from the tar file missing.  Quietly. 

Ahhh, dawn brightens my perception, but I will only be extracting _one_
file at a time, with the -p switch, to stdout, which is redirected to a
unique filename, (subroutine I developed years ago, builds unique
filenames out of the current date and time). After preforming the
attempted extraction, I open the file for random access and check LOF, if
it's greater that zero, success, else failure.

Anyway, ran into a problem when trying to rebuild djtar with a quiet
switch, can't directly GCC it, and have only convinced make to produce
this message so far using the make file:

gcc @../../gcc.opt -I. -I- -I../../../include  -c unzip.c
gcc.exe: @../../gcc.opt: No such file or directory (ENOENT)
make.exe: *** [unzip.o] Error 1

So the question arises, just how much of the source do I have to unpack?!