X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.4 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,FORGED_YAHOO_RCVD,FREEMAIL_FROM,KHOP_THREADED,NML_ADSP_CUSTOM_MED,RCVD_NUMERIC_HELO,SPF_HELO_PASS,TW_YG,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Andrew Stein Subject: Re: 1.7.11-1 Update returns non-zero exit codes for coreutils Date: Fri, 30 Mar 2012 18:49:08 +0000 (UTC) Lines: 44 Message-ID: References: <20120328170130 DOT M51882 AT ds DOT net> <4F7347D2 DOT 8050308 AT cygwin DOT com> <20120328172709 DOT M58531 AT ds DOT net> <20120330010734 DOT M64805 AT ds DOT net> <4F7527B8 DOT 2020404 AT cygwin DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Larry Hall (Cygwin cygwin.com> writes: > > On 3/29/2012 9:10 PM, Brian Wilson wrote: > > From: Andrew > >> > >> I just got this exact same thing and tried re-installing coreutils > >> with no effect. Initially, I had been installing binutils, and was > >> told to restart because I had left a cygwin console open during the > >> install. Interested to hear what is known about this (recent) issue. > >> > > > > Interesting... I didn't have any consoles open (that I remember) during the > > update, but I've rebooted and done an update since this issue surfaced (again > > with no console open) and it hasn't resolved. I've been wondering if I should > > remove the C:\cygwin directories and try installing again. I'm hoping I won't > > have to do something that drastic. > > I'd recommend making sure all Cygwin processes are stopped (including > services) and try installing the cygwin and coreutils package again, > along with anything else you'd like to include. If you're still having > problems, cygcheck output will be helpful in any follow-up. > So, Larry, are you talking about un-/reinstalling cygwin entirely*? Also, does cygwin dev monitor this chat in case this is a bug? If not, is there a better place to report such an issue? Couple of other points. In searching some of the error codes (eg. "command not found" message), I also added "c:\cygwin\bin" to my PATH and created env variable CYGWIN_HOME as "c:\cygwin". This stopped the "command not found" message, though ls output was still empty. Thanks. *If so (ie. most likely the quickest path to resolution), I'm still a more than happy customer, and cygwin is still in the 99.9999999% satisfaction realm. Can't recall ever having an update issue like this before, but them's the breaks with software! :) -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple