X-Spam-Check-By: sourceware.org
Message-ID: <45E041DB.90709@byu.net>
Date: Sat, 24 Feb 2007 06:47:07 -0700
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.9) Gecko/20061207 Thunderbird/1.5.0.9 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com, bozho AT kset DOT org
Subject: Re: tar/gzip outside of bash problem
References: <45DEDB9E DOT 100 AT kset DOT org>
In-Reply-To: <45DEDB9E.100@kset.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

-----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?

> 
> I have updated my packages (including tar and gzip), and the problem persists.
> Attached is a cygcheck.out after the update.

Nothing obvious jumped out at me, other than the fact that your PATH has a
potentially problematic first entry, and that you use textmode mounts even
for known binary directories such as /usr/bin, which is not recommended.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF4EHb84KuGfSFAYARAt0TAJ0d5ef5ScNXn49ziUzxJuHWMoilcgCghU81
/LJTOk2MAdDhC82kQkl7wno=
=WQQI
-----END PGP SIGNATURE-----

--
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/