Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID: <3D28B547.5020201@beamreachnetworks.com>
Date: Sun, 07 Jul 2002 14:40:23 -0700
From: "Eric M. Monsler" <emonsler AT beamreachnetworks DOT com>
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.4.1) Gecko/20020314 Netscape6/6.2.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: Paul Pitot <ppitot AT oktal DOT fr>
CC: cygwin AT cygwin DOT com
Subject: Re: Shells and makefiles are still very slow with cygwin
References: <000501c224db$f7c4c1e0$0200a8c0 AT duron850>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Paul Pitot wrote:

> Shells and makefiles are still very slow with cygwin
> 
> I use cygwin for about 2 years and do not see any real response to this
> simple question :
> Why a simple shell script like this is so slow ?



I'm sorry, I just can't stand idly by in the face of the previous 
sarcastic replies.

I figure that you deserve a more helpful reply, one that might actually 
(someday) make it run nearly as fast as a native POSIX environment.

Additionally, it might help future users who are searching the archives, 
trying desperately to find a way to get lighting fast shell script and 
makefile execution.

The problem is that YOU, yes YOU, have not downloaded the sources, 
profiled and identified the slow parts, and contributed SUS and POSIX-ly 
correct speed-up patches to the cygwin project.


HTH.



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/