X-Spam-Check-By: sourceware.org Message-ID: Date: Mon, 23 Apr 2007 19:19:25 -0400 From: "Michael D. Adams" To: cygwin AT cygwin DOT com Subject: Re: Setup.exe Problems on Vista In-Reply-To: <462C0C88.F09E959B@dessent.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <462B002F DOT A1E27066 AT dessent DOT net> <462C0C88 DOT F09E959B AT dessent DOT net> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 4/22/07, Brian Dessent wrote: > 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. I tried a fresh install of cygwin (after stashing away the old version (with move, but I skipped the unmoust since I use the default mounts anyway)) with setup.exe version 2.562 (from the snapshots). Oddly, while sh.exe is now being created and the prompt is the colored one that Cygwin usually sets, /etc/passwd is not being created. I am uncertain whether this is the same bug manifested in a new way or if it might be a new bug. (Obligatory grumble about Vista being a pain.) Did you check your /etc/passwd? I only noticed it b/c when I started the shell my home directory was set to C:\Users\ instead of C:\cygwin\home\. (C:\Users is Vista's version of what in XP is C:\Documents and Settings.) Michael D. Adams mdmkolbe AT gmail DOT com -- 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/