Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <551CAE7F65D2D211A67E0008C7A4A99E0502E3@exchny25.sbi.com>
From: "Whitney, John" <john DOT whitney AT ssmb DOT com>
To: "'Mumit Khan'" <khan AT thor DOT xraylith DOT wisc DOT EDU>
Cc: cygwin AT sourceware DOT cygnus DOT com
Subject: RE: RE: why gcc.exe compilation SLOW on NT? 
Date: Fri, 1 Oct 1999 15:09:22 -0400 
X-Mailer: Internet Mail Service (5.5.2650.10)

Mumit,

You were exactly right.  My NT server DOES mount alot of network drives.  I
trimmed the "unnecessaries" off my PATH and gcc.exe compiled the source in
at most a couple of seconds,
both in bash and on the dos command line.

Thanks again,
John

-----Original Message-----
From: Mumit Khan [mailto:khan AT thor DOT xraylith DOT wisc DOT EDU]
Sent: Thursday, September 30, 1999 8:01 PM
To: Whitney, John
Cc: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: why gcc.exe compilation SLOW on NT? 


John Whitney <john DOT whitney AT ssmb DOT com> 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