Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-Id: <4.3.1.2.20010206145452.019ba320@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Tue, 06 Feb 2001 14:58:21 -0500 To: Bernard Dautrevaux , "'VanRossem, James'" From: "Larry Hall (RFK Partners, Inc)" Subject: RE: Problem w/ cygwin tar.exe: Unable to tar directories beginnin g w/ the letter 'R' in NT 4.0 Cc: "GnuWin32 Mailing List (Adresse de messagerie)" In-Reply-To: <17B78BDF120BD411B70100500422FC6309E1F1@IIS000> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 02:23 PM 2/6/2001, Bernard Dautrevaux wrote: > > -----Original Message----- > > From: VanRossem, James > > [mailto:James DOT VanRossem AT exchange DOT fleetsecurities DOT com] > > Sent: Tuesday, February 06, 2001 8:30 PM > > To: Bernard Dautrevaux > > Subject: RE: Problem w/ cygwin tar.exe: Unable to tar directories > > beginnin g w/ the letter 'R' in NT 4.0 > > > > > > hi bernard, thanks for all your help. > > With regards to your comment, i'm invoking > > cygwin tar from the 'cmd' prompt under windows NT 4.0 > > I don't think it's the sh/bash shell. In which case, the > > '\' should not be an escape character. Apparently, you're > > correct in that > > if i use forward slashes, > > it seems to work and if I use double backslashes it seemed to > > work also. > > I'm still confused on why that is, since this > > is an NT environment and '\' should work. (I don't run tar in the > > pseudo-UNIX environment) > > I just copy the tar.exe, gzip.exe and cygwin1.dll file to the > > directory i'm > > using, (for testing purposes) > > and call tar from there (the NT command prompt). > > GNU tar works fine, but > > Cygwin tar can't work with single '\', do you have any ideas why? > > thanks again, > >My best guess would be that, if invoked from cmd, Cygwin tools will try to >'glob' their arguments (that is expand *, ? and other meta-characters). I've >not looked at the code but I suspect that cygwin, in this case, is expanding >escape sequences (so that for example you can have an explicit * in an >argument) and will gobble the single backslashes (and convert \r to a CR) > >Does anybody with knowledge of this part of the code could confirm or infirm >this ? sorry, I cannot check it myself now; it's getting late here in Paris >and I'm going to come back home :-) No, its not Cygwin. If it were, other tools with this same path would have the same problem. They don't. Also note that the problem is with 1 backslash: D:\tmp\AshishCode>tar cvf file.tgz d:\tmp\AshishCode\DeProxyBridgeDependency.cpp tar: Cannot add file d: mp\AshishCode\DeProxyBridgeDependency.cpp: No such file or directory tar: Error exit delayed from previous errors This bug is in tar. Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 118 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple