This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
RE: why must cygwin be first in path?
- To: Steven Schram <sschram at aircell dot com>, Bob McGowan <Robert dot McGowan at veritas dot com>
- Subject: RE: why must cygwin be first in path?
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- Date: Fri, 4 Feb 2000 08:15:46 -0800 (PST)
- Cc: cygwin at sourceware dot cygnus dot com
- Reply-To: earnie_boyd at yahoo dot com
--- Steven Schram <sschram@aircell.com> 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 <mailto:earnie_boyd@yahoo.com>
Cygwin Newbies, please visit
<http://www.freeyellow.com/members5/gw32/index.html>
__________________________________________________
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@sourceware.cygnus.com