Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Tue, 16 Mar 2004 11:47:03 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin problems with Hyperthreaded machines? Message-ID: <20040316164703.GD21715@redhat.com> 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.4.1i On Tue, Mar 16, 2004 at 10:55:14AM -0500, Chuck McDevitt wrote: >I've been running into some severe problems with using Cygwin on >Hyperthreaded machines. > >The problem mostly occurs when capturing the stdout from a program with >the backquote operator, >or using the shell command in makefiles. The captured values end up as >blank sometimes. > >For example, in my Makefile, > > source-dir := $(strip $(shell pwd)) > >pwd always returns something, but source-dir sometimes gets set to an >empty string. > >This never happens on single-CPU non-hyperthreaded machines. > >I've also seen occasional hangs during a make, again only on hyperthreaded >machines. > >I've tried the latest cygwin dll from cygwin.com, as well as the snapshot >from 3/12, and I still get this problem. > >Anyone else out there seeing this? Is this a known problem? Is there >some version of the cygwin dll that doesn't have this problem? It's not a known problem and you are not providing enough details to track the problem down. http://cygwin.com/problems.html -- Christopher Faylor spammers: aaaspam AT sourceware DOT org Cygwin Project Leader Red Hat, Inc. -- 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/