On Sat, Feb 24, 2007 at 06:47:07AM -0700, Eric Blake wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >According to Marko Bozikovic on 2/23/2007 5:18 AM: >> Hi all, >> >> I've just come across a strange problem. When I try to unpack a tar.gz >> archive >> in cmd.exe, I get an error: >> >> tar (child): gzip: Cannot exec: No such file or directory >> tar (child): Error is not recoverable: exiting now >> tar: Child returned status 2 >> tar: Error exit delayed from previous errors >> >> The command line I use is: >> tar zxvf archive.tar.gz > >It worked for me. > >> >> When running the same command from bash, it works ok. >> >> I have found this mail: >> http://cygwin.com/ml/cygwin/2006-08/msg00038.html >> >> but it's not applicable to my case, since I have no empty entries in the >> PATH. > >But you DO have an entry with spaces and parenthesis; perhaps cygwin's >path-conversion routines are being confused by that? Can you compare >'echo $PATH' under bash vs. 'set PATH' under cmd? How about 'env | >grep "^PATH"' under cmd?
Why would Cygwin's path conversion routines be confused by spaces or parentheses? They are just ASCII characters. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
