Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <20000204161546.5339.qmail@web109.yahoomail.com> Date: Fri, 4 Feb 2000 08:15:46 -0800 (PST) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: RE: why must cygwin be first in path? To: Steven Schram , Bob McGowan Cc: cygwin AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- Steven Schram wrote: > How fast is your test computer? In my case, bash takes no perceptible time > to start -- no matter whether cygwin1.dll is currently loaded or has been > loaded recently. On the other hand, make starts quickly but pauses before > processing the Makefile only if the PATH is arranged 'incorrectly' and only > if the pause hasn't occurred in the last 10 seconds. It seems important to > note that the delay happens every 10 seconds even if make is executed > repeatedly. Also, it need not be executed from an interactive shell. I use > Visual SlickEdit and it executes make via a non-interactive cmd.exe shell. > The delay does occur in this case. > So, exactly what are _you_ using Cygwin for? Are you using the POSIX layer of Cygwin? What happens if you modify the make command to be "sh -c 'make'"? Do you see the same results when executing make from bash? Regards, ===== Earnie Boyd Cygwin Newbies, please visit __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com