why must cygwin be first in path?

Steven Schram sschram@aircell.com
Fri Feb 4 07:43:00 GMT 2000


I can access files in system32 just fine.

The simplest case I have done that fails is
PATH=c:\;d:\cygnus\cygwin-b20\H-i586-cygwin32\bin;(...rest of path)

It seems to not matter if there are a lot of files in the preceding
directories.

Steve

-----Original Message-----
From: Tony Karakashian [ mailto:tonyk@genbrew.com ]
Sent: Thursday, February 03, 2000 11:23 AM
To: 'Steven Schram'; cygwin@sourceware.cygnus.com
Subject: RE: why must cygwin be first in path?


This IS odd.  I have seen some cases where the path, etc will become screwed
up because things like %systemroot%\system32, etc aren't the first items in
the path.  What ends up happening is it can't find things like net.exe, ,
notepad...and then, even if you explicitely place the system32 directory in
the path, it STILL can't find anything in there.  Do you have that problem?
How many items in YOUR path and the system path before the cygwin directory?
What happens if you put it second or third?  The items in your path prior to
cygwin, are they stuffed full with files the system has to wade through
before cygwin?  If the directory paths are cached, that would explain the 10
second search the first time, then it shrinks to 3.

-T

> The only way I have found to get GNU Make to execute properly from the NT
Command Shell is to put > the cygwin directory first in the PATH variable.
Otherwise, 'make.exe' has that strange delay
> (about 3  seconds) I mentioned a while back.  Does this give anyone a clue
as to why there is
> a delay at all?


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com



More information about the Cygwin mailing list