This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: version 1.3 10, problem with gunzip.exe
- From: "Larry Hall (RFK Partners, Inc)" <lhall at rfk dot com>
- To: "Donszelmann, Mark" <duns at SLAC dot Stanford dot EDU>, "'cygwin at cygwin dot com'" <cygwin at cygwin dot com>
- Date: Mon, 20 May 2002 13:23:40 -0400
- Subject: Re: version 1.3 10, problem with gunzip.exe
- References: <2846497B437BF84BAD1A4CC407418D26694BC9@exchange1.slac.stan ford.edu>
At 01:13 PM 5/20/2002, Larry Hall (RFK Partners, Inc) wrote:
>At 12:53 PM 5/20/2002, Donszelmann, Mark wrote:
> >Version 1.3.10 net installation of cygwin seems to have the following problem:
> >
> >gunzip.exe seems to be only 19 bytes long and does not run.
>
>
>It's a symbolic link and you apparently have "nowinsymlinks" in your
>CYGWIN environment variable. You either need to unset that and recreate
>the symbolic links (and others referring to executables on your system) or
>always run these from a shell like bash that understands Cygwin symbolic
>links (not windows shortcuts).
Actually, this may be overstating the case a tad:
1. The above is true if "nowinsymlinks" is set.
2. I believe setup.exe creates symbolic links as if "nowinsymlinks" is
set. So setup would create the symbolic links as Cygwin symlinks
rather than Windows shortcuts regardless of the setting in the
CYGWIN environment variable.
3. Running gunzip from a non-Cygwin aware shell (like cmd.exe or
command.com) would require specifying the name of the symlink recreated
as a shortcut. In this case, that means "gunzip.exe.lnk".
I think that covers it. Someone will tell me if (2) is wrong. :-)
Larry Hall lhall@rfk.com
RFK Partners, Inc. http://www.rfk.com
838 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/