This is the mail archive of the
mailing list for the Cygwin project.
RE: RE: why gcc.exe compilation SLOW on NT?
- To: "'Mumit Khan'" <khan at thor dot xraylith dot wisc dot EDU>
- Subject: RE: RE: why gcc.exe compilation SLOW on NT?
- From: "Whitney, John" <john dot whitney at ssmb dot com>
- Date: Fri, 1 Oct 1999 15:09:22 -0400
- Cc: cygwin at sourceware dot cygnus dot com
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.
From: Mumit Khan [mailto:email@example.com.EDU]
Sent: Thursday, September 30, 1999 8:01 PM
To: Whitney, John
Subject: Re: why gcc.exe compilation SLOW on NT?
John Whitney <firstname.lastname@example.org> 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
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.
Want to unsubscribe from this list?
Send a message to email@example.com