X-Spam-Check-By: sourceware.org
Message-ID: <462C0C88.F09E959B@dessent.net>
Date: Sun, 22 Apr 2007 18:31:52 -0700
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Setup.exe Problems on Vista
References: <c62c8d860704211850p64ebd2b1y79c063a9d2a4fb26 AT mail DOT gmail DOT com> <462B002F DOT A1E27066 AT dessent DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
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

Brian Dessent wrote:

> > The workaround for this problem that I have found is to set the
> > *Windows* path to include C:\cygwin\bin before running setup.exe.  So
> > for example this sequence works:
> >
> > set PATH=C:\cygwin\bin;%PATH%
> > setup.exe
> >
> > Then /bin/sh is actually created, the prompt is the usual Cygwin settings, etc.
> > Of course the proper solution would be to find and fix the root cause.
> >  Is this a known bug?  Is there any other info I can provide to help
> > find the root cause? (I'm suspicious that Vista might not allow the
> > program to set PATH.)
> 
> That would be pretty brain dead if Vista did not allow programs to
> modify the PATH.  That would cause about a million failures in Cygwin
> and various programs.
> 
> > OS: Vista Home Premium
> > Setup.exe Version: 2.510.2.2 (run without administraitor permission)
> 
> Please try the latest setup.exe snapshot, if you can.  And even better
> would be to debug the problem.  I don't have access to a Vista system
> but if I did I think I would start by running it under gdb/insight and
> putting a breakpoint at script.cc:run() right before CreateProcess and
> check the environment.  Or create a test package with a postinstall that
> just runs "env > /tmp/foo" or "sleep 1h" or something so that you can
> inspect the environment.

Just now I installed Vista under VMware to try installing Cygwin.  It
worked fine using the latest version of setup.exe.  I did not have to
disable UAC but it did prompt me to run as Administrator (which it does
for any executable named setup.exe IIRC.)  Postinstall scripts all ran
fine, sh.exe was there and there was no need to put \cygwin\bin in the
PATH manually.

Brian

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