Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: 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: <199910291704.MAA18484@pluto.xraylith.wisc.edu> To: manus AT eiffel DOT com cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: C compilation slow on NT In-Reply-To: Your message of "Fri, 29 Oct 1999 09:15:51 PDT." Date: Fri, 29 Oct 1999 12:04:22 -0500 From: Mumit Khan "Emmanuel STAPF" writes: > Sorry to bother you guys. I read a thread not too long ago about the poor > performance of gcc on Windows NT. I was trying to find the solution given in > the mailing list archive, but it is not easy due to the poor search > possibilities offered by the web page. > > Can someone send me what has to be modified so that gcc does not do lookup > on the network? Thanks in advance. > > Otherwise, I notice that make was slow too. Any idea? > The trick is to make sure that network drives are not in your PATH, and also that you have HOME defined correctly and it's not '/'. On NT, these could be in the registry and can stay hidden. The trouble with HOME is the following: let's say you HOME=/ defined in the environment. Some of the tools, eg. gdb, tries to find startup files in $HOME/, and some of these append an extra '/' and so it expands to '//' and that's a UNC path. Takes a while before it times out. Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com