X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 15 Mar 2010 12:29:21 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Cygwin 1.7: Concurrency Issue with Shared State Initialization Message-ID: <20100315162921.GA30463@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) 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 Mon, Mar 15, 2010 at 11:01:04AM +0100, Schmidt, Oliver wrote: >Hi Christopher, > >> Also, one big thing is missing here: cygcheck output [...] >> Please send that ASAP. > >Please find attached the requested information. However I had to edit >it - as carefully as possible - to omit hints on the SAP-internal IT >infrastructure. Thanks. It would be nice if we could come up with some way to make cygcheck not output sensitive information but I doubt that there's any foolproof heuristic that we could use and, if we added an option, people might trust it unduly. >The sporadic failures I reported originally were experienced too by >colleagues running 1.7.1 on Vista-32 and Vista-64. They too can avoid >it by running the Cygwin shell in another window during the build. No one is doubting that problems exist. That's why we're working on them. cgf -- 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