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: <199910010000.TAA12150@pluto.xraylith.wisc.edu> To: John Whitney cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: why gcc.exe compilation SLOW on NT? In-Reply-To: Your message of "Thu, 30 Sep 1999 19:31:51 EDT." <37F3F2E7 DOT 80E4A4C5 AT ssmb DOT com> Date: Thu, 30 Sep 1999 19:00:57 -0500 From: Mumit Khan John Whitney writes: > Hey Folks, > > I didn't expect my "helloworld.c" program to take 10 minutes to compile > via cygwin's gcc.exe (version egcs-2.91.57) on my NT machine. The > compile did complete and the resulting exe does run, but why so long to > compile? Check your PATH to make sure there're not network/UNC paths in it. Start a bash console window, reset your PATH to the minimum necessary and see if that fixes the problem. A common problem is when you have bunch of Novell or NT servers in your PATH and collect2 checks those to find the subprograms it needs to run, and ends up spending lots of time waiting on the servers. It's not unique to NT of course -- same happens with Unix if you're using NFS/AFS/etc. fyi, when you report these problems, it's always good have to provide more information, such as the output of `cygcheck -s -r'. Yours is certainly an "environment" related problem. Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com